I'm out of my depth here but I understand there have been some
attempts to explain the outage as a promulgation of change applied.
I don't know how that occurs and whether the promulgation is staged
effect or a torrent of dispersal.
Whilst it appears as a pandemic, is that demographic view a
representation of dispersal of contagion or dispersed access to the contagion?
Are there any points of service not subject to contagion and therefore
might constitute a discrete or sovereign locale?
I know nothing about the network, but can a sovereign locale exist as
hubs...
Surely there will be a lot of discussion in due time.
On 13 Nov 2026, dolf <dolfboek@hotmail.com> posted some news:nlnucjFj20pU1@mid.individual.net:
I'm out of my depth here but I understand there have been some
attempts to explain the outage as a promulgation of change applied.
I don't know how that occurs and whether the promulgation is staged
effect or a torrent of dispersal.
Whilst it appears as a pandemic, is that demographic view a
representation of dispersal of contagion or dispersed access to the
contagion?
Are there any points of service not subject to contagion and therefore
might constitute a discrete or sovereign locale?
I know nothing about the network, but can a sovereign locale exist as
hubs...
Surely there will be a lot of discussion in due time.
"Root Cause: Microsoft reported that a configuration update caused
systems to fail automated health checks, pulling servers offline and cascading a heavy traffic load onto remaining infrastructure. Microsoft
has confirmed the incident is not the result of a cybersecurity breach."
Their efforts to resolve the issues caused additional I/O flapping and bottlenecks as servers attempting to recover overwhelmed those that were operational. There's one big choke party going on at Microsoft right
now.
If you'd like more specific details per application or service, have a
peek at the UPenn Computing link below. They are publishing the updates
from Microsoft they are receiving.
https://mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-inc idents.html?q=EX1550543
No ETA for full recovery at this time.
--
Deer Microsoft board of directors, this is what you get when you hire
from India.
Thank you for the information...
I also note that you allude to a slap-dash cultural disposition ...
Wes <wes@formerlystk.com> wrote:
On 13 Nov 2026, dolf <dolfboek@hotmail.com> posted some
news:nlnucjFj20pU1@mid.individual.net:
I'm out of my depth here but I understand there have been some
attempts to explain the outage as a promulgation of change applied.
I don't know how that occurs and whether the promulgation is staged
effect or a torrent of dispersal.
Whilst it appears as a pandemic, is that demographic view a
representation of dispersal of contagion or dispersed access to the
contagion?
Are there any points of service not subject to contagion and therefore
might constitute a discrete or sovereign locale?
I know nothing about the network, but can a sovereign locale exist as
hubs...
Surely there will be a lot of discussion in due time.
"Root Cause: Microsoft reported that a configuration update caused
systems to fail automated health checks, pulling servers offline and
cascading a heavy traffic load onto remaining infrastructure. Microsoft
has confirmed the incident is not the result of a cybersecurity breach."
Their efforts to resolve the issues caused additional I/O flapping and
bottlenecks as servers attempting to recover overwhelmed those that were
operational. There's one big choke party going on at Microsoft right
now.
If you'd like more specific details per application or service, have a
peek at the UPenn Computing link below. They are publishing the updates
from Microsoft they are receiving.
https://mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-inc
idents.html?q=EX1550543
No ETA for full recovery at this time.
--
Deer Microsoft board of directors, this is what you get when you hire
from India.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 61:00:57 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,219 |