Mailing List Archive: Google Fiber IPv4 routing issue

Google Fiber IPv4 routing issue

May 6, 2021, 7:24 AM

Post #1 of 3 (340 views)

Google Fiber (from Huntsville, AL) seems to be having a routing issue to
things west - at least Linode Dallas and AWS us-west-2. It only seems
to be affecting IPv4. Traceroutes to affected networks from GFiber go
one hop past my home router and stop, and a traceroute from a Linode in
Dallas hits GFiber's Equinix Dallas peering and stops (v6 to/from the
same host works).

Not sure if this is affecting other GFiber cities, but since things are
stopping at their edge, I'd expect so.
--
Chris Adams <cma@cmadams.net>
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: Google Fiber IPv4 routing issue [ In reply to ]

outages at outages

May 6, 2021, 7:32 AM

Post #2 of 3 (340 views)

Permalink

> On May 6, 2021, at 9:24 AM, Chris Adams via Outages <outages@outages.org> wrote:
>
> Google Fiber (from Huntsville, AL) seems to be having a routing issue to
> things west - at least Linode Dallas and AWS us-west-2. It only seems
> to be affecting IPv4. Traceroutes to affected networks from GFiber go
> one hop past my home router and stop, and a traceroute from a Linode in
> Dallas hits GFiber's Equinix Dallas peering and stops (v6 to/from the
> same host works).
>
> Not sure if this is affecting other GFiber cities, but since things are
> stopping at their edge, I'd expect so.

Looks like a local issue for you. I’m on Google Fiber in Austin, and my mail server lives in Linode Dallas. IPv4 and IPv6 are both good.

—Chris
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: Google Fiber IPv4 routing issue [ In reply to ]

outages at outages

May 6, 2021, 8:54 AM

Post #3 of 3 (340 views)

Permalink

Once upon a time, Chris Boyd <cboyd@gizmopartners.com> said:
> > On May 6, 2021, at 9:24 AM, Chris Adams via Outages <outages@outages.org> wrote:
> > Google Fiber (from Huntsville, AL) seems to be having a routing issue to
> > things west - at least Linode Dallas and AWS us-west-2. It only seems
> > to be affecting IPv4. Traceroutes to affected networks from GFiber go
> > one hop past my home router and stop, and a traceroute from a Linode in
> > Dallas hits GFiber's Equinix Dallas peering and stops (v6 to/from the
> > same host works).
> >
> > Not sure if this is affecting other GFiber cities, but since things are
> > stopping at their edge, I'd expect so.
>
>
> Looks like a local issue for you. I’m on Google Fiber in Austin, and my mail server lives in Linode Dallas. IPv4 and IPv6 are both good.

Maybe it was just Huntsville routes then... but it's back working now.
--
Chris Adams <cma@cmadams.net>
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages