Re: Zayo woes

[Randy Carpenter]

The problem we have run into is that there does not appear to be a "Zayo." 
There are dozens of acquisitions of regional providers with completely 
different infrastructure and teams and they have done a very poor job at gluing 
it all together. I have seen service orders that have gone *years* without 
being complete. There are also currently some 
breaking-the-entire-regional-network sorts of outages going on currently. I am 
guessing what clued employees they still have are quite tied up.


-Randy


- On Sep 18, 2023, at 7:06 PM, JASON BOTHE via NANOG nanog@nanog.org wrote:

> Does anyone know what’s happening at Zayo? Tickets are taking weeks and months
> to get resolved, much less get a tech assigned to them.
> 
> The folks answering the noc phone are mere order takers and are only reading
> from a script, manager on duty/escalation lines go to voicemail.
> 
> If anyone can help get to a human in the transport group, that would be great.
> I’ve given up all hope at this point.
> 
> Appreciated.
> 
> Jason

Zayo woes

[JASON BOTHE via NANOG]

Does anyone know what’s happening at Zayo? Tickets are taking weeks and months 
to get resolved, much less get a tech assigned to them. 

The folks answering the noc phone are mere order takers and are only reading 
from a script, manager on duty/escalation lines go to voicemail. 

If anyone can help get to a human in the transport group, that would be great. 
I’ve given up all hope at this point. 

Appreciated. 

Jason 

Re: Contact at VuDu

[John Stitt]

I’ve been trying to reach someone at Vudu with the exact same problem. So far 
haven’t had any luck.

John Stitt
HES Energynet

Sent from my iPhone

> On Sep 18, 2023, at 2:45 PM, Brad Bendy  wrote:
> 
> Can anyone at VuDu contact me off list? Have issues with some new
> subnets we have and our end users cannot access the VuDu service with
> various error messages.
> 
> Thanks
> 
> CAUTION: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe. If you are not expecting this message contact the sender 
> directly via phone/text to verify.
> 

Contact at VuDu

[Brad Bendy]

Can anyone at VuDu contact me off list? Have issues with some new
subnets we have and our end users cannot access the VuDu service with
various error messages.

Thanks

Re: Providing geofeed info to Google

[Robert Story]

Try putting it in your whois. More info on how this works and how to do
it here:

   https://geolocatemuch.com/

Regards,
Robert

--
USC Information Sciences Institute 
Networking and Cybersecurity Division


On Mon 2023-09-18 13:17:49+0300 Hank wrote:
> Old topic: if one doesn't have access to https://isp.google.com how
> does one update their geo-location data so Google sees it?
> 
> Thanks,
> 
> Hank
> 
> > 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
> >> https://mailman.nanog.org/pipermail/nanog/2015-May/075229.html.
> >>
> >> Is that still the case?  Are there any avenues to provide Google
> >> with geofeed info if you're *not* currently peering with 15169? Or
> >> to get access to just the geofeed update portion of the Peering
> >> Portal?  

Re: Providing geofeed info to Google

[Hank Nussbacher]

Old topic: if one doesn't have access to https://isp.google.com how does 
one update their geo-location data so Google sees it?



Thanks,

Hank


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
https://mailman.nanog.org/pipermail/nanog/2015-May/075229.html.

Is that still the case?  Are there any avenues to provide Google with
geofeed info if you're *not* currently peering with 15169? Or to get access
to just the geofeed update portion of the Peering Portal?