4 ms·

I hope these kind of “ipv4” only outages encourages more and more websites to upgrade to ipv6. #OutageBenefit ;)

eskaytwo 6y ago
It would appear from the limited info so far, to be an issue in the v4 routing configuration - I haven’t seen anything that says this couldn’t have been the other way around.
cuu508 6y ago
Sadly, in my experience, ipv4 is generally more reliable than ipv6 still. Set up two hosts, host A and host B in two different data centers. Make them send HTTP requests to each other over ipv4 and over ipv6. You'll see that latency spikes, packet loss is more frequent over ipv6.
- bigdict 6y ago
  Why is that?
  - chaboud 6y ago
    We’ve observed this in end-user devices, especially on some ISPs. It makes sense if the overall adoption and resource allocation are comparatively smaller, making individual or small-group coincident spikes more impactful against the amortized whole. It’s a lot like a market with low volume/liquidity. Someone wanders in with a big transaction and blows everything up.
iso1210 6y ago
Few people care if ipv6 breaks so it doesn't make headlines
itguy4321365 6y ago
This doesn't have anything to do with IPv4 vs IPv6. It is a routing issue with BGP. To give an analogy, if every website were a house, and every house has a house number (IP address-- either IPv4 or IPv6), and a group of houses form cities and towns that can be identified by a number (AS/ Atonomous System number), the highways between cities are similar to BGP routes, and if half of the world's internet traffic goes through the city of Centurylink (AS3356), If the city of CenturyLink (AS3356) shut down traffic, either on purpose or on accident. ...then it doesn't matter if your house number / IP address is a 32bit number or a 128bit number because traffic needs to take a different route. This is what everyone is worried about BGP routes, not IP addresses.

It would appear from the limited info so far, to be an issue in the v4 routing configuration - I haven’t seen anything that says this couldn’t have been the other way around.

cuu508 6y ago

Sadly, in my experience, ipv4 is generally more reliable than ipv6 still. Set up two hosts, host A and host B in two different data centers. Make them send HTTP requests to each other over ipv4 and over ipv6. You'll see that latency spikes, packet loss is more frequent over ipv6.

bigdict 6y ago
Why is that?
- chaboud 6y ago
  We’ve observed this in end-user devices, especially on some ISPs. It makes sense if the overall adoption and resource allocation are comparatively smaller, making individual or small-group coincident spikes more impactful against the amortized whole. It’s a lot like a market with low volume/liquidity. Someone wanders in with a big transaction and blows everything up.

iso1210 6y ago

Few people care if ipv6 breaks so it doesn't make headlines

itguy4321365 6y ago

This doesn't have anything to do with IPv4 vs IPv6. It is a routing issue with BGP. To give an analogy, if every website were a house, and every house has a house number (IP address-- either IPv4 or IPv6), and a group of houses form cities and towns that can be identified by a number (AS/ Atonomous System number), the highways between cities are similar to BGP routes, and if half of the world's internet traffic goes through the city of Centurylink (AS3356), If the city of CenturyLink (AS3356) shut down traffic, either on purpose or on accident. ...then it doesn't matter if your house number / IP address is a 32bit number or a 128bit number because traffic needs to take a different route. This is what everyone is worried about BGP routes, not IP addresses.