#rogersoutage We observed a few rounds of recovery attempts and fraction of traffic came back multiple times. But none of the recovery lasted over one hour. The network went completely down again at around 23:00 UTC. More in the updated blog post: blog.cloudflare.com/cloudflares-vi…
As described in the blog post, we also saw a pattern of #BGP route flapping in the form of large number of announcements followed by withdrawals. This could indicate internal/core network issue getting propagated out via BGP.
The traffic starts to ramp up again! A bunch of curious engineers here (virtually) are watching the traffic monitors and cheer to see higher throughput. It's been 40 minutes now, and it seems to be able to sustain the load this time.
The network recovery process seem plateaued, and it carries less than 20% of what it carried yesterday same time. We still see comparable and number of BGP announcements and withdrawals now, which indicates the core network issue has not been resolved yet.
#rogersoutage Partial recovery. See how much data it carries as compared to 24 hours ago in graphs here.
#rogersoutage Rogers traffic rate remains increasing slowly for the past hour, now reaching 22% comparing to the rate 24 hours ago.
#rogersoutrage Here is a graph showing Rogers' traffic slowly climbing back up for the past 4 hours. I also saw reports of people getting their phone and Internet access back. I hope this means the outage is over.
Here is graph showing the #BGP message volume for the past 2 days during #rogersoutage observed from @Cloudflare vantage points. The outage started at 08:30 UTC on Friday and ends starting at 00:00 UTC on Saturday (when we start to see traffic ramping up).
@Cloudflare @CloudflareRadar also provides public dashboard for you to keeps tap on how much traffic we are seeing as compared to a week ago. We can see that the traffic has come back to the normal rate now. You can access the graph for Rogers here: radar.cloudflare.com/asn/812?date_f…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Mingwei Zhang 🦀

Mingwei Zhang 🦀 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @heymingwei

Feb 11
There was a significant jump on announcement of this prefix at the time of the event.
stat.ripe.net/widget/bgp-upd… Image
AS7625 announces a /21 that covers the prefix in question (/24). AS9457 also announces a super prefix, but even larger (/16 as oppose to /21). Techinically, it should be fine for either ASNs to originate the prefix in question. But it's a bit stranger for AS9457 to do so. Image
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(