Looks like it's just cleared up for me. On 6/9/2020 6:54 PM, Charles Sprickman via Outages wrote: > I think that’s not what people are seeing, probably more of this sort > of thing: > > PING softlayer.ip (softlayer.ip): 56 data bytes > Request timeout for icmp_seq 0 > Request timeout for icmp_seq 1 > 64 bytes from softlayer.ip: icmp_seq=2 ttl=46 time=361.999 ms > Request timeout for icmp_seq 3 > 64 bytes from softlayer.ip: icmp_seq=4 ttl=46 time=353.756 ms > 64 bytes from softlayer.ip: icmp_seq=5 ttl=46 time=355.315 ms > Request timeout for icmp_seq 6 > 64 bytes from softlayer.ip: icmp_seq=7 ttl=46 time=355.523 ms > Request timeout for icmp_seq 8 > Request timeout for icmp_seq 9 > Request timeout for icmp_seq 10 > Request timeout for icmp_seq 11 > Request timeout for icmp_seq 12 > Request timeout for icmp_seq 13 > 64 bytes from softlayer.ip: icmp_seq=14 ttl=46 time=350.946 ms > Request timeout for icmp_seq 15 > ^C > --- softlayer.ip ping statistics --- > 17 packets transmitted, 5 packets received, 70.6% packet loss > round-trip min/avg/max/stddev = 350.946/355.508/361.999/3.635 ms > > >> On Jun 9, 2020, at 7:39 PM, Jeff P via Outages <[email protected] >> <mailto:[email protected]>> wrote: >> >> https://cloud.ibm.com/status/ >> ================================= >> MAINTENANCE: IBM Cloud Monitoring will be unavailable during maintenance >> *Component: *IBM Cloud Monitoring with Sysdig >> *Location: *London >> *Start time: *9 Jun 2020 3:00 PM >> *End time: *9 Jun 2020 6:00 PM >> *Update time: *1 Jun 2020 12:19 PM >> ------------------------------------------------------------------------ >> *Type: *Maintenance >> *ID: *CHG0683971 >> >> *What are we changing?* >> >> 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. >> >> >> *Why are we making this change?* >> >> 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. >> >> >> *How will it impact the environment?* >> >> 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. >> >> >> *Maintenance Duration*: 180 minutes >> ================================================= >> >> JeffP >> [email protected] <mailto:[email protected]> >> >> >> * >> Please consider the environment before printing this e-mail.* >> >> NOTICE: >> 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. >> >> >> >> >> On Tue, Jun 9, 2020 at 4:15 PM James Brown via Outages >> <[email protected] <mailto:[email protected]>> wrote: >> >> 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? >> >> -- >> James Brown >> Network Engineer >> _______________________________________________ >> Outages mailing list >> [email protected] <mailto:[email protected]> >> https://puck.nether.net/mailman/listinfo/outages >> >> _______________________________________________ >> Outages mailing list >> [email protected] <mailto:[email protected]> >> https://puck.nether.net/mailman/listinfo/outages > > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
