ServiceNow

Anyone else having issues getting to service now? We use it for ticketing: montana.servicenowservices.com [149.96.184.230]. Im not seeing it in our internet routers nor on a couple of looking glass servers.

Re: BendTel ASN27008 moving router tonight

On Tue, 30 Aug 2022 10:37:40 -0700 Tim Howe wrote: > Between 9 and 11pm tonight our colo provider must move our router to a > new rack. > I'll shut down bgp a bit after 9pm and then restore once I verify the > router is back up correctly and interfaces are normalized. > Everything

Re: RFC: BOGONs over BGP, adding some ranges

On Tue, Aug 30, 2022 at 10:17 AM James Shank wrote: > > Dear NANOG! > > As many of you know, Team Cymru runs a free service delivering updated > BOGONS to networks around the world. We've been doing this for decades > at this point. For more information about this service, please see >

Re: RFC: BOGONs over BGP, adding some ranges

I would love to see this via BGP personally Not sure of anything that it could cause - and folks could filter out something if needed/required *Glenn S. Kelley, *I am a Connectivity.Engineer Text and Voice Direct: 740-206-9624 a Division of CreatingNet.Works

Re: RFC: BOGONs over BGP, adding some ranges

Hi John! Thanks for the comments! If you're in Hollywood for N86, perhaps we can pour one our for multicast together... ;) Cheers! James On 8/30/22 4:21 PM, John Kristoff wrote: On Tue, 30 Aug 2022 13:15:40 -0400 James Shank wrote: 224/4 If any were to cause a problem, I'd think this

Re: Providing geofeed info to Google

Good call, thanks. That appears to be via the assigned resources bit ("IP Addresses" heading in Arin Online). Will give that a shot, thanks! -- Hugo Slabbert On Tue, Aug 30, 2022 at 1:38 PM Job Snijders wrote: > On Tue, Aug 30, 2022 at 01:28:18PM -0700, Hugo Slabbert wrote: > > @Job: > > > >

Re: Providing geofeed info to Google

On Tue, Aug 30, 2022 at 01:28:18PM -0700, Hugo Slabbert wrote: > @Job: > > Thanks! I was aware of the RIPE whois option, but the relevant resources > for us are in ARIN. I wasn't aware of the RPSL *remark* option for > providing that. We should be able to give that a bash. Hmmm, there might be

Re: Providing geofeed info to Google

Gonna multi-reply on this one: @Benjamin: > I was able to get access without peering with 15169 by getting access to the ISP portal (isp.google.com) which does have Geofeed processing for my AS, but I am unsure if you will get access without being an eyeball network. Thanks; I'll give that

Re: RFC: BOGONs over BGP, adding some ranges

On Tue, 30 Aug 2022 13:15:40 -0400 James Shank wrote: > 224/4 If any were to cause a problem, I'd think this is the one that would be most likely. While inter-domain IP multicast is practically dead and so the impact might not be so great (sorry multicast-wg and mboned friends), there may be

Re: Providing geofeed info to Google

Dear Hugo, On Tue, Aug 30, 2022 at 12:34:41PM -0700, Hugo Slabbert wrote: > Google folks: > > I see historical reference to needing to use the Google Peering Portal ( > http://peering.google.com) if you need to provide Google with geofeed info > for GeoIP info on network blocks, ref >

Re: Providing geofeed info to Google

For what it's worth I attempted to get access by filling out the same portal and was told to go pound sand, so your results may very. On 2022-08-30 12:40, Benjamin Hatton wrote: I was able to get access without peering with 15169 by getting access to the ISP portal (isp.google.com

Re: Providing geofeed info to Google

I was able to get access without peering with 15169 by getting access to the ISP portal (isp.google.com) which does have Geofeed processing for my AS, but I am unsure if you will get access without being an eyeball network. On Tue, Aug 30, 2022 at 3:37 PM Hugo Slabbert wrote: > Google folks: >

Providing geofeed info to Google

Google folks: I see historical reference to needing to use the Google Peering Portal ( http://peering.google.com) if you need to provide Google with geofeed info for GeoIP info on network blocks, ref https://mailman.nanog.org/pipermail/nanog/2015-May/075229.html. Is that still the case? Are

BendTel ASN27008 moving router tonight

Between 9 and 11pm tonight our colo provider must move our router to a new rack. I'll shut down bgp a bit after 9pm and then restore once I verify the router is back up correctly and interfaces are normalized. -- Tim Howe ti...@bendtel.com Data Processing541-389-8252 BendTel

RFC: BOGONs over BGP, adding some ranges

Dear NANOG! As many of you know, Team Cymru runs a free service delivering updated BOGONS to networks around the world. We've been doing this for decades at this point. For more information about this service, please see https://www.team-cymru.com/bogon. Recently, we've discussed internally

Re: Amprnet? (was Re: [anti-abuse-wg] Yet another BGP hijacking towards AS16509)

Yeah, ARDC sold part of it to Amazon. I doubt they even had right to do so due to 44/8 was an legacy IP range.. ARIN allowed it.. All too shady. Anyway, according to AMPRnet that range was unallocated, so no active radio ham networks were at that range, so I doubt it was someone from AMPRnet.