Dated, sourced changes that affect working on Starlink: network latency, IP policy, business plans, major outages and the monthly reliability report.https://starlinkremotework.com/https://starlinkremotework.com/news/2026-10-01-slack-free-plan-message-sending-blocked/https://starlinkremotework.com/news/2026-10-01-slack-free-plan-message-sending-blocked/From 5:39 to 11:59 a.m. PDT on October 1, 2026 (8:39 a.m. to 2:59 p.m. EDT), some Slack workspaces on the free plan could not send messages. Slack said a feature toggle ramp-up made an app integration post messages in a loop, which pushed free-plan workspaces over their message limit and triggered the sending block; Slack then lifted the block for all affected workspaces. Small teams on the free plan saw what looked like a broken connection, but the internet was fine. (Event date 2026-10-01. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-09-28-starship-deploys-first-26-starlink-v3-satellites/https://starlinkremotework.com/news/2026-09-28-starship-deploys-first-26-starlink-v3-satellites/On September 28, 2026, Starship reached orbit for the first time and deployed 26 Starlink V3 satellites, each with about 1 Tbps of downlink and 160 Gbps of uplink capacity, according to Light Reading. SpaceX said it made contact with all 26 and expects them to start serving customers within a few weeks after checks. Twenty-six satellites are a small share of a constellation of thousands, so don’t expect a change at your desk yet. (Event date 2026-09-28. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2026-08-31-microsoft-365-authentication-outage/https://starlinkremotework.com/news/2026-08-31-microsoft-365-authentication-outage/Starting at 15:08 UTC (11:08 a.m. EDT) on August 31, 2026, Microsoft 365 users had trouble with Exchange Online email, Teams, OneDrive, SharePoint and other services, tracked as incident MO1465074. Microsoft linked it to an issue in a core authentication configuration shared across services, and recovery ran into the next day. Sign-in failures can look like a broken VPN or a home internet problem; check Microsoft’s status first. Published October 6, 2026. (Event date 2026-08-31. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-08-20-google-cloud-us-west1-outage-fiber-maintenance/https://starlinkremotework.com/news/2026-08-20-google-cloud-us-west1-outage-fiber-maintenance/From 08:00 to 10:22 Pacific time on August 20, 2026 (11:00 a.m. to 1:22 p.m. EDT), many Google Cloud services in the us-west1 region in Oregon had elevated latency, errors and failures. Google’s incident report says scheduled fiber optic maintenance unexpectedly cut network capacity between its data centers there and automatic rerouting did not shift traffic properly. Business apps hosted in that region could fail for remote workers even when their home connections were fine. Published October 6, 2026. (Event date 2026-08-20. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-07-23-microsoft-365-outage-network-configuration-change/https://starlinkremotework.com/news/2026-07-23-microsoft-365-outage-network-configuration-change/For about three hours and 42 minutes on July 23, 2026 (roughly 10:44 a.m. to 2:26 p.m. EDT), Microsoft 365 users whose traffic ran through North America had trouble with Teams, SharePoint Online, OneDrive and other services, tracked as incident MO1437424. Microsoft said a recent network configuration change might be contributing, reverted it, and moved traffic onto other network paths. As of October 6, 2026 we had not found a public post-incident report. (Event date 2026-07-23. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-05-30-google-workspace-outage-gmail-meet-drive/https://starlinkremotework.com/news/2026-05-30-google-workspace-outage-gmail-meet-drive/From 20:15 to 21:30 Pacific time on Saturday, May 30, 2026 (11:15 p.m. to 12:30 a.m. EDT), Gmail, Google Calendar, Chat, Docs, Drive, Meet and Google Voice had trouble loading or completing tasks. Google’s incident report says failures in a cluster component behind its service discovery and configuration systems, triggered by a high volume of rapid configuration changes, caused the disruption. Few US workers were at their desks, but anyone working late saw failures on every kind of connection. Published October 6, 2026. (Event date 2026-05-30. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-05-27-slack-outage-cascading-scheduling-failure/https://starlinkremotework.com/news/2026-05-27-slack-outage-cascading-scheduling-failure/Starting at 22:21 UTC on May 27, 2026 (6:21 p.m. EDT), Slack users worldwide had trouble with messaging, workflows, apps, integrations, canvases and connections. Slack said that following an infrastructure change, a cascading scheduling failure caused the impact; services were largely back to normal late that night Pacific time, and leftover permission problems were fixed at 14:13 UTC on May 28. It was a Slack failure, not a home internet one. Published October 6, 2026. (Event date 2026-05-27. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-05-05-ookla-starlink-us-median-latency-39-ms-q1-2026/https://starlinkremotework.com/news/2026-05-05-ookla-starlink-us-median-latency-39-ms-q1-2026/An Ookla report published May 5, 2026 says US Starlink Speedtest users had a median multi-server latency of 39 ms in Q1 2026, with median downloads of 127.39 Mbps and uploads of 21.46 Mbps. It also says 10 states had a median under 40 ms in the second half of 2025, up from one state a year earlier. These are crowd-sourced speed test medians, not call-quality or work-hour measurements. Published October 6, 2026. (Event date 2026-05-05. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2026-02-20-cloudflare-byoip-outage/https://starlinkremotework.com/news/2026-02-20-cloudflare-byoip-outage/From 17:56 to 23:03 UTC (12:56 to 6:03 p.m. EST) on February 20, 2026, a buggy cleanup task at Cloudflare withdrew about 1,100 Bring Your Own IP prefixes, around a quarter of the total. Services using those addresses, which can include company VPN gateways and remote-access portals, could not be reached from any internet connection. The 1.1.1.1 resolver kept answering DNS queries; only its website showed errors. Published October 6, 2026. (Event date 2026-02-20. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-01-22-cloudflare-ipv6-route-leak-miami/https://starlinkremotework.com/news/2026-01-22-cloudflare-ipv6-route-leak-miami/From 20:25 to 20:50 UTC (3:25 to 3:50 p.m. EST) on January 22, 2026, a misconfigured router in Cloudflare’s Miami data center advertised IPv6 routes it should not have. Cloudflare said this caused packet loss and higher latency between Miami and Atlanta and that it dropped traffic for some outside networks; only IPv6 was affected. Starlink gives every plan IPv6, so IPv6-only problems can reach Starlink homes even when IPv4 works. Published October 6, 2026. (Event date 2026-01-22. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-01-22-microsoft-365-outage-north-america/https://starlinkremotework.com/news/2026-01-22-microsoft-365-outage-north-america/From about 2:30 p.m. ET on January 22, 2026, Microsoft 365 users in North America had trouble with Exchange Online email, SharePoint and OneDrive file search, and Teams chat and meetings. Microsoft said part of its service infrastructure in North America was not processing traffic as expected. A home internet problem looks the same from your desk, so check the vendor’s status before restarting your router. Published October 6, 2026. (Event date 2026-01-22. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-01-14-verizon-wireless-outage-about-10-hours/https://starlinkremotework.com/news/2026-01-14-verizon-wireless-outage-about-10-hours/Starting around noon ET on January 14, 2026, many Verizon wireless customers lost calls and data until Verizon said the outage was resolved at 10:15 p.m. ET. Verizon blamed a software issue and offered affected customers a $20 credit. Anyone whose failover plan relied on a Verizon hotspot or phone tethering lost that backup for most of a work day, which is why a backup line should be on a different network from anything else you depend on. Published October 6, 2026. (Event date 2026-01-14. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2026-01-09-fcc-approves-7500-more-starlink-gen2-satellites/https://starlinkremotework.com/news/2026-01-09-fcc-approves-7500-more-starlink-gen2-satellites/On January 9, 2026, the FCC approved SpaceX’s request for 7,500 more Gen2 Starlink satellites, bringing the approved Gen2 total to 15,000, and granted more spectrum and higher power in some bands. Half of the new satellites must be deployed by the end of 2028 and the rest by the end of 2031. More satellites and spectrum add capacity over years, not overnight. Published October 6, 2026. (Event date 2026-01-09. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2026-01-03-starlink-2025-progress-report-26-ms-median-latency/https://starlinkremotework.com/news/2026-01-03-starlink-2025-progress-report-26-ms-median-latency/Starlink’s 2025 progress report, covered by DishyTech on January 3, 2026, gives a global median latency of about 26 ms, peak-hour downloads above 200 Mbps and uploads typically above 30 Mbps, and says it added about 4.6 million customers in 2025. These are company-wide medians, not US-only or per-connection numbers. Published October 6, 2026. (Event date 2026-01-03. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2026-01-01-starlink-to-lower-4400-satellites-to-480-km/https://starlinkremotework.com/news/2026-01-01-starlink-to-lower-4400-satellites-to-480-km/On January 1, 2026, Starlink VP of engineering Michael Nicolls said Starlink will lower about 4,400 satellites, all of those near 550 km, to about 480 km over 2026. The stated reason is space safety: failed satellites fall out of orbit much faster at the lower height. Starlink has not published any latency change tied to the move, so watch the numbers rather than expect a difference. Published October 6, 2026. (Event date 2026-01-01. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2025-12-05-cloudflare-outage-25-minutes/https://starlinkremotework.com/news/2025-12-05-cloudflare-outage-25-minutes/From 08:47 to 09:12 UTC (3:47 to 4:12 a.m. EST) on December 5, 2025, about 28% of the HTTP traffic Cloudflare serves failed after a configuration change triggered an error in its proxy software. It was short and came before the US work day, but it was the second Cloudflare outage in three weeks. Published October 6, 2026. (Event date 2025-12-05. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-11-18-cloudflare-outage-bot-management-file/https://starlinkremotework.com/news/2025-11-18-cloudflare-outage-bot-management-file/From 11:20 to 17:06 UTC (6:20 a.m. to 12:06 p.m. EST) on November 18, 2025, Cloudflare’s core network returned errors for many sites it serves. Cloudflare said a database permissions change doubled the size of a Bot Management feature file, which crashed the software that routes traffic. Cloudflare Access, which some employers use for remote logins, was among the affected products. Published October 6, 2026. (Event date 2025-11-18. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-10-29-azure-front-door-outage-microsoft-365/https://starlinkremotework.com/news/2025-10-29-azure-front-door-outage-microsoft-365/From 15:41 UTC on October 29 to 00:05 UTC on October 30, 2025 (11:41 a.m. to 8:05 p.m. EDT), Azure Front Door, Microsoft’s global front-end network, had connectivity problems across regions. Microsoft’s incident record lists Microsoft 365, Microsoft Entra ID and the Azure Portal among affected services and traces it to incompatible configuration metadata that exposed a latent bug. Remote workers on Teams and Outlook could not fix this from home. Published October 6, 2026. (Event date 2025-10-29. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-10-20-aws-us-east-1-outage-dns-race-condition/https://starlinkremotework.com/news/2025-10-20-aws-us-east-1-outage-dns-race-condition/From 11:48 p.m. PDT on October 19 to 2:20 p.m. PDT on October 20, 2025, AWS services in its Northern Virginia (US-EAST-1) region failed in stages. AWS’s own summary traces it to a race condition in DynamoDB’s automated DNS management that left an empty DNS record. Apps built on AWS failed for users on every kind of connection, so a backup internet line would not have helped. Published October 6, 2026. (Event date 2025-10-20. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-07-24-starlink-global-outage-core-network-software/https://starlinkremotework.com/news/2025-07-24-starlink-global-outage-core-network-software/Starting around 3 p.m. ET on July 24, 2025, Starlink customers in the US and many other countries lost service for about 2.5 hours. Starlink’s VP of engineering, Michael Nicolls, said the outage was caused by a failure of key internal software services that operate the core network. Because no setting on the dish helps when the core network fails, a backup line on a different network is the only thing that would have kept a work day going. Published October 6, 2026. (Event date 2025-07-24. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-07-16-starlink-reports-25-7-ms-us-median-peak-hour-latency/https://starlinkremotework.com/news/2025-07-16-starlink-reports-25-7-ms-us-median-peak-hour-latency/In a network update posted July 16, 2025, Starlink said that as of June 2025 it was delivering a median peak-hour latency of 25.7 ms across all US customers, with a goal of a steady 20 ms median. A median says nothing about the short spikes and drops that freeze calls, so it doesn’t replace a per-hour view of one connection. Published October 6, 2026. (Event date 2025-07-16. Network changes affecting latency.)Tue, 06 Oct 2026 12:00:00 GMTNetwork changes affecting latencyhttps://starlinkremotework.com/news/2025-07-14-cloudflare-1111-dns-resolver-outage/https://starlinkremotework.com/news/2025-07-14-cloudflare-1111-dns-resolver-outage/From 21:52 to 22:54 UTC (5:52 to 6:54 p.m. EDT) on July 14, 2025, Cloudflare’s 1.1.1.1 resolver, including 1.0.0.1, was unavailable after an internal configuration error. Anyone whose router or computer used only those addresses for DNS saw websites and apps fail even though the Starlink link itself was up. Setting a second resolver from a different provider avoids this single point of failure. Published October 6, 2026. (Event date 2025-07-14. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-06-12-google-cloud-outage-hits-workspace-and-cloud-apps/https://starlinkremotework.com/news/2025-06-12-google-cloud-outage-hits-workspace-and-cloud-apps/From 10:51 a.m. to about 6:18 p.m. PDT on June 12, 2025, a crash in Google Cloud’s Service Control system caused 503 errors across many Google Cloud products and Google Workspace. The same afternoon, Cloudflare said a third-party cloud provider’s storage failure broke WARP connections and Access logins for about two and a half hours. For a remote worker this looked like “my internet is down” even though home connections were fine. Published October 6, 2026. (Event date 2025-06-12. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-04-16-zoom-domain-blocked-by-registry-meetings-down/https://starlinkremotework.com/news/2025-04-16-zoom-domain-blocked-by-registry-meetings-down/From 2:25 to 4:12 p.m. EDT on April 16, 2025, the zoom.us domain stopped working because GoDaddy Registry placed a block on it. GoDaddy Registry said a communication error between Zoom’s registrar, Markmonitor, and the registry caused the shutdown, and that there was no product, security or network failure. Meetings, Zoom Phone and Zoom’s website failed for users on every kind of connection, so restarting a home router would not have helped. Published October 6, 2026. (Event date 2025-04-16. Major outages and post-mortems.)Tue, 06 Oct 2026 12:00:00 GMTMajor outages and post-mortemshttps://starlinkremotework.com/news/2025-03-19-starlink-priority-plans-become-local-and-global-priority/https://starlinkremotework.com/news/2025-03-19-starlink-priority-plans-become-local-and-global-priority/Starlink replaced its fixed-location Priority plan with Local Priority and its Mobile Priority plan with Global Priority, moving existing customers at their next billing period. Priority data became a monthly block; once it is used up, speeds drop to about 1 Mbps down and 500 kbps up unless more is bought. Offices using Starlink as a main or backup line should check which block they are on. (Event date 2025-03-19. Business plan changes.)Tue, 06 Oct 2026 12:00:00 GMTBusiness plan changes