<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I think that’s not what people are seeing, probably more of this sort of thing:<div class=""><br class=""></div><div class="">PING softlayer.ip (softlayer.ip): 56 data bytes<br class="">Request timeout for icmp_seq 0<br class="">Request timeout for icmp_seq 1<br class="">64 bytes from softlayer.ip: icmp_seq=2 ttl=46 time=361.999 ms<br class="">Request timeout for icmp_seq 3<br class="">64 bytes from softlayer.ip: icmp_seq=4 ttl=46 time=353.756 ms<br class="">64 bytes from softlayer.ip: icmp_seq=5 ttl=46 time=355.315 ms<br class="">Request timeout for icmp_seq 6<br class="">64 bytes from softlayer.ip: icmp_seq=7 ttl=46 time=355.523 ms<br class="">Request timeout for icmp_seq 8<br class="">Request timeout for icmp_seq 9<br class="">Request timeout for icmp_seq 10<br class="">Request timeout for icmp_seq 11<br class="">Request timeout for icmp_seq 12<br class="">Request timeout for icmp_seq 13<br class="">64 bytes from softlayer.ip: icmp_seq=14 ttl=46 time=350.946 ms<br class="">Request timeout for icmp_seq 15<br class="">^C<br class="">--- softlayer.ip ping statistics ---<br class="">17 packets transmitted, 5 packets received, 70.6% packet loss<br class="">round-trip min/avg/max/stddev = 350.946/355.508/361.999/3.635 ms<br class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 9, 2020, at 7:39 PM, Jeff P via Outages <<a href="mailto:outages@outages.org" class="">outages@outages.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">
<div class="gmail-summary-item gmail-summary-title"><a href="https://cloud.ibm.com/status/" class="">https://cloud.ibm.com/status/</a><br class=""></div><div class="gmail-summary-item gmail-summary-title">=================================<br class=""></div><div class="gmail-summary-item gmail-summary-title">MAINTENANCE: IBM Cloud Monitoring will be unavailable during maintenance</div><div class="gmail-summary-item"><b class="">Component: </b>IBM Cloud Monitoring with Sysdig</div><div class="gmail-summary-item"><b class="">Location: </b>London</div><div class="gmail-summary-item"><b class="">Start time: </b>9 Jun 2020 3:00 PM</div><div class="gmail-summary-item"><b class="">End time: </b>9 Jun 2020 6:00 PM</div><div class="gmail-summary-item"><b class="">Update time: </b>1 Jun 2020 12:19 PM</div><hr class=""><div class="gmail-summary-item"><b class="">Type: </b>Maintenance</div><div class="gmail-summary-item"><b class="">ID: </b>CHG0683971</div><div class="gmail-description-item gmail-summary-item"><span class=""><p class=""><strong class="">What are we changing?</strong></p><p class="">We
are introducing changes to the IBM Cloud Monitoring with Sysdig service
which require database maintenance that will require up to 30 minutes
of downtime for the service.</p><br class=""><p class=""><strong class="">Why are we making this change?</strong></p><p class="">We
are making changes to our service infrastructure to improve the service
stability and to improve our ability to release non-disruptive changes
in the future. These changes to our data storage infrastructure require
an outage to ensure that customer data is not impacted by these changes.</p><br class=""><p class=""><strong class="">How will it impact the environment?</strong></p><p class="">During
the maintenance window there will be up to 30 minutes of downtime while
we perform the database maintenance. During this time the service will
not be available. There will be gaps in the metric data once the
service is restored for the outage period during the maintenance
window. Alerting will be unavailable during the downtime and there may
be some alerts triggered after the downtime due to the missing metric
data depending on your alert configurations.</p><br class=""><b class="">Maintenance Duration</b>: 180 minutes<br class=""></span></div>
<div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">=================================================</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">JeffP<br class="">j<a href="mailto:jeffp@jeffp.us" target="_blank" class="">effp@jeffp.us</a><br class=""><br class=""><br class=""><div style="text-align:center" class=""><span style="font-family:arial black,sans-serif" class=""><b class=""><font size="4" class=""><br class="">Please consider the environment before printing this e-mail.</font></b></span><br class=""></div><br class="">NOTICE:<br class="">This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Use or dissemination by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail to correct our records. Please then delete the original message (including any attachments) in its entirety, including any backup processes that your system may perform. Please note that any views or opinions presented in this email are solely those of the author. Email transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.<br class=""><br class=""><br class=""></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 9, 2020 at 4:15 PM James Brown via Outages <<a href="mailto:outages@outages.org" class="">outages@outages.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div class="gmail_default" style="font-family:times new roman,serif">It looks like IBM Cloud / SoftLayer / NetworkLayer is having a global outage since about 15:04 Pacific time affecting routing to AWS, Level 3 / CenturyLink, and a bunch of other providers. Has anyone been able to get more details?</div><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><span style="font-family:times new roman,serif" class="">James Brown</span><div class=""><span style="font-family:times new roman,serif" class=""><span class="gmail_default" style="font-family:"times new roman",serif">Network </span>Engineer</span></div></div></div></div></div></div>
_______________________________________________<br class="">
Outages mailing list<br class="">
<a href="mailto:Outages@outages.org" target="_blank" class="">Outages@outages.org</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank" class="">https://puck.nether.net/mailman/listinfo/outages</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Outages mailing list<br class=""><a href="mailto:Outages@outages.org" class="">Outages@outages.org</a><br class="">https://puck.nether.net/mailman/listinfo/outages<br class=""></div></blockquote></div><br class=""></div></body></html>