Identifying widespread outages using atlas?
Hi I'm wondering if there is any good statistic tool that helps identyfing any widespread Internet outages using ripe atlas probes such as ISP issues (like todays http://www.bbc.co.uk/news/technology-36844712), cable cuts, etc. Normally I select probe and look into public measurements but it does not seem to be very effective. ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/>
On 20/07/16 14:46, Rafal.Jankowski@thomsonreuters.com wrote:
Hi I’m wondering if there is any good statistic tool that helps identyfing any widespread Internet outages using ripe atlas probes such as ISP issues (like todays http://www.bbc.co.uk/news/technology-36844712), cable cuts, etc. Normally I select probe and look into public measurements but it does not seem to be very effective.
yes, this is still an active topic of research. we've made some inroads into anomaly detection and RIPE Atlas traceroutes (http://arxiv.org/abs/1605.04784), and there is work in progress on making data from that available near-realtime. we do have a live-stream of probe connect/disconnect events (docs at: https://atlas.ripe.net/docs/result-streaming/ ), and are also working on detecting outage-type signals from that. and we do one-off analysis of events, examples: https://labs.ripe.net/Members/emileaben/internet-access-disruption-in-turkey https://labs.ripe.net/Members/emileaben/does-the-internet-route-around-damag... that said, we can help investigate particular events, if we expect the outcome to yield interesting data/insight to our community. cheers, Emile Aben
Emile, Thank you for your response, that's lot of interesting reading. By the way I tried to follow one of the links from your articles: https://labs.ripe.net/Members/cristel_pelsser/pinpointing-delay-and-forwardi... but it seems to have endless HTTP redirection loop (screenshot attached) So please correct me if I'm wrong but except for the http://atlas-stream.ripe.net API there is no tool for end user to detect massive disruptions but you are working on it and can help with investigations if you find the case interesting? What would be the good address to discuss observed Internet outages, would it be this mailing list? By the way what is the preferred quoting style here. Is it top posting or is it better to reply inline? Is it ok to use RTF/HTML formatted e-mails or should we keep them in clean plain text? Regards, Rafał -----Original Message----- From: Emile Aben [mailto:emile.aben@ripe.net] Sent: Wednesday, July 20, 2016 3:02 PM To: Jankowski, Rafal (Financial&Risk); ripe-atlas@ripe.net Subject: Re: [atlas] Identifying widespread outages using atlas? On 20/07/16 14:46, Rafal.Jankowski@thomsonreuters.com wrote:
Hi I'm wondering if there is any good statistic tool that helps identyfing any widespread Internet outages using ripe atlas probes such as ISP issues (like todays https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bbc.co.uk_news_technology-2D36844712&d=CwIDEA&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=uSdRM1m6v9tUqQwN60nzfridakyp61O-UW1qUYv1tD30FWDjrpwJLIAUAzixBHEl&m=5Z3UBNnSbSlYNxkm4daW5IWTFOymc9kWmslsB9BB6FA&s=R-eUK6LIyFAWRqJFzf0kcTZlSyhZMWrdwUcZ5224mFc&e= ), cable cuts, etc. Normally I select probe and look into public measurements but it does not seem to be very effective.
yes, this is still an active topic of research. we've made some inroads into anomaly detection and RIPE Atlas traceroutes (https://urldefense.proofpoint.com/v2/url?u=http-3A__arxiv.org_abs_1605.04784&d=CwIDEA&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=uSdRM1m6v9tUqQwN60nzfridakyp61O-UW1qUYv1tD30FWDjrpwJLIAUAzixBHEl&m=5Z3UBNnSbSlYNxkm4daW5IWTFOymc9kWmslsB9BB6FA&s=6v3gFLshi6q1A59mMGda4KF2UatbRQwaEl309nBMOfQ&e= ), and there is work in progress on making data from that available near-realtime. we do have a live-stream of probe connect/disconnect events (docs at: https://urldefense.proofpoint.com/v2/url?u=https-3A__atlas.ripe.net_docs_result-2Dstreaming_&d=CwIDEA&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=uSdRM1m6v9tUqQwN60nzfridakyp61O-UW1qUYv1tD30FWDjrpwJLIAUAzixBHEl&m=5Z3UBNnSbSlYNxkm4daW5IWTFOymc9kWmslsB9BB6FA&s=lfTSWyrtr1sUJolSXZG39CASEyDt2NTBc8dB8gwO3Ks&e= ), and are also working on detecting outage-type signals from that. and we do one-off analysis of events, examples: https://urldefense.proofpoint.com/v2/url?u=https-3A__labs.ripe.net_Members_emileaben_internet-2Daccess-2Ddisruption-2Din-2Dturkey&d=CwIDEA&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=uSdRM1m6v9tUqQwN60nzfridakyp61O-UW1qUYv1tD30FWDjrpwJLIAUAzixBHEl&m=5Z3UBNnSbSlYNxkm4daW5IWTFOymc9kWmslsB9BB6FA&s=PysqQZMBZEFJyG9eRri5na69aiwD1PIj_7tjFJxYwgQ&e= https://urldefense.proofpoint.com/v2/url?u=https-3A__labs.ripe.net_Members_emileaben_does-2Dthe-2Dinternet-2Droute-2Daround-2Ddamage&d=CwIDEA&c=4ZIZThykDLcoWk-GVjSLm9hvvvzvGv0FLoWSRuCSs5Q&r=uSdRM1m6v9tUqQwN60nzfridakyp61O-UW1qUYv1tD30FWDjrpwJLIAUAzixBHEl&m=5Z3UBNnSbSlYNxkm4daW5IWTFOymc9kWmslsB9BB6FA&s=-e_e9VuElKj5S0jQePMj7uryH4KzZHXx0I3jwUB2KfM&e= that said, we can help investigate particular events, if we expect the outcome to yield interesting data/insight to our community. cheers, Emile Aben
Hi Rafał, On 20/07/16 16:03, Rafal.Jankowski@thomsonreuters.com wrote:
Emile,
Thank you for your response, that's lot of interesting reading.
By the way I tried to follow one of the links from your articles: https://labs.ripe.net/Members/cristel_pelsser/pinpointing-delay-and-forwardi...
but it seems to have endless HTTP redirection loop (screenshot attached)
Apologies for that. I'll ask our web team to take a look at this.
So please correct me if I'm wrong but except for the http://atlas-stream.ripe.net API there is no tool for end user to detect massive disruptions but you are working on it and can help with investigations if you find the case interesting? What would be
Yes, that sounds like a good summary. Others will comment if i missed something of course. We had some nice hackathon projects on visualising probe disconnects (for instance https://github.com/RIPE-Atlas-Community/ripe-atlas-halo/tree/master/src/halo), but as far as i understand these took the raw signal and didn't do any additional statistical processing, which is something we have under research currently.
the good address to discuss observed Internet outages, would it be this mailing list?
There is a mailing list dedicated to discuss Internet outages (https://puck.nether.net/mailman/listinfo/outages); the specific GB outage you referred to earlier has been discussed there some: https://puck.nether.net/pipermail/outages/2016-July/009281.html
By the way what is the preferred quoting style here. Is it top posting or is it better to reply inline? Is it ok to use RTF/HTML formatted e-mails or should we keep them in clean plain text?
I prefer inline, and plain text, and i have a sense that many share that preference. cheers, emile
participants (2)
-
Emile Aben -
Rafal.Jankowski＠thomsonreuters.com