Third Party Index

Snapshot 27046

Document
Status page
URL
https://status.uptime.com/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
browser
Size
451008 bytes
SHA-256 (raw)
530dfa6050ef131a452a7991fc56c458d347f50434e0581fb5cc465fab7cbb36
SHA-256 (normalized text)
822e70b121e6b4af3521fedca288be42876014eca7690329963703f26f4336c2

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Auto-Refresh
Some systems are experiencing issues
All Events
Vault secret updates not propagating to monitoring nodesSep 22, 2026 18:00 GMT — ongoing (8d 18h)
InvestigatingSep 22, 2026 18:00:00 GMT
Summary
Since September 22 at 18:00 UTC, changes to secrets in Vault have not been reaching the monitoring nodes. This started after checks moved to the new check manager. Checks that use Vault secrets keep running with the last value each node had before the move. If a secret has been rotated or changed since then, checks using it may fail or report wrong results. The issue is still ongoing.
Impact
Affected: checks that use Vault secrets (credentials, tokens, headers, variables) and whose secret was updated after the migration
Not affected: checks that don't use Vault secrets, and checks whose secrets haven't changed since the migration
What users see: [false DOWN alerts or authentication failures on checks using rotated credentials / no visible effect for most accounts]
Duration: ongoing, about 9 days so far (since September 22 at 18:00 UTC)
Affected Components
Secure Vault
Singapore, Australia-Sydney - Monitoring IP MismatchOct 01, 2026 01:00 GMT — ongoing (10h 56m)
MonitoringOct 01, 2026 08:41:58 GMT
Servers were re-attached to the original IPs. We are monitoring the situation
InvestigatingOct 01, 2026 01:00:00 GMT
Summary
Some checks from the Singapore and Australia-Sydney locations used IP addresses that are not on our published list. If your firewall only allows our published IP addresses, these checks can fail and cause false DOWN alerts. We are still confirming the IP addresses used in Sydney.
Affected IP Addresses
Country - City	Family	Old IP (published)	New IP (observed)
Singapore - Singapore	IPv4	139.162.35.94	172.104.47.196
Singapore - Singapore	IPv6	2400:8901:e001:56b::1	2400:8901::2000:efff:fec3:d889
Australia - Sydney	IPv4	172.105.167.54
Australia - Sydney	IPv6	2400:8907:e001:303::1
Impact
Only some checks from Singapore-Singapore and Sydney-Australia are affected. Other locations work normally. The published IP addresses have not changed.
Next Update
We will send an update when the issue is resolved.
Affected Components
Australia-Sydney
Singapore-Singapore
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning - 07 October 2026Oct 07, 2026 00:00 GMT — Oct 07, 2026 23:59 GMT (1d 0h)
Scheduled MaintenanceOct 07, 2026 00:00:00 GMT
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning
Date: October 7, 2026
Impact: No monitoring downtime. Action may be required if you allowlist our probe IPs.
What is happening
As part of ongoing infrastructure improvements, on October 7, 2026 we are retiring a set of legacy checking node IP addresses across several probe locations. Monitoring from these locations continues without interruption from replacement addresses.
Which customers are affected
Only customers who allowlist (whitelist) our probe IP addresses on firewalls, WAFs, CDNs, or origin servers are affected.
If you do not filter traffic by source IP, no action is needed.
Action required
Remove the addresses listed below from your allowlists.
IP addresses being decommissioned
Location	Addresses
USA - Los Angeles, CA	149.28.86.208
2001:19f0:6001:429d:5400:4ff:fe5e:b37f
66.165.229.42
2604:4500:8:115::4
46.21.152.34
2604:4500:8:122::4
23.227.177.154
2604:4500:8:10::4
37.72.173.250
2604:4500:8:15::4
94.100.20.50
2604:4500:8:8::4
66.165.228.130
2604:4500:8:100::4
149.255.35.194
2604:4500:8:1c5::4
66.165.243.98
2604:4500:8:2c::4
USA - New York, NY	144.202.10.128
2001:19f0:c:1332:5400:4ff:fe5e:b368
64.176.218.171
2001:19f0:0:4b99:5400:4ff:feff:c60a
198.178.224.231
2605:6440:4000:3::5
198.178.224.9
2605:6440:4000:3::6
185.209.179.215
2605:6440:4000:2::24
198.178.224.89
2605:6440:4000:3::8
198.178.224.98
2605:6440:4000:3::9
69.67.151.188
2605:6440:4000:3::11
69.67.151.230
2605:6440:4000:3::10
160.202.128.189
2605:6440:4007:41::2
160.202.128.181
2605:6440:4007:3d::2
Germany - Frankfurt	108.61.210.50
2001:19f0:6c01:b3e:5400:4ff:fedb:eab7
66.206.3.90
2604:4500:c:e::4
66.206.3.98
2604:4500:c:11::4
45.158.38.66
2604:4500:c:13::4
Singapore - Singapore	45.76.185.158
2001:19f0:4400:63d6:5400:4ff:feff:c5db
Questions
If you need help updating your allowlists, contact [email protected] and we will assist.
Plain-text copy of all decommissioned addresses
149.28.86.208 66.165.229.42 46.21.152.34 23.227.177.154 37.72.173.250 94.100.20.50 66.165.228.130 149.255.35.194 66.165.243.98 2001:19f0:6001:429d:5400:4ff:fe5e:b37f 2604:4500:8:115::4 2604:4500:8:122::4 2604:4500:8:10::4 2604:4500:8:15::4 2604:4500:8:8::4 2604:4500:8:100::4 2604:4500:8:1c5::4 2604:4500:8:2c::4 144.202.10.128 64.176.218.171 198.178.224.231 198.178.224.9 185.209.179.215 198.178.224.89 198.178.224.98 69.67.151.188 69.67.151.230 160.202.128.189 160.202.128.181 2001:19f0:c:1332:5400:4ff:fe5e:b368 2001:19f0:0:4b99:5400:4ff:feff:c60a 2605:6440:4000:3::5 2605:6440:4000:3::6 2605:6440:4000:2::24 2605:6440:4000:3::8 2605:6440:4000:3::9 2605:6440:4000:3::11 2605:6440:4000:3::10 2605:6440:4007:41::2 2605:6440:4007:3d::2 108.61.210.50 66.206.3.90 66.206.3.98 45.158.38.66 2001:19f0:6c01:b3e:5400:4ff:fedb:eab7 2604:4500:c:e::4 2604:4500:c:11::4 2604:4500:c:13::4 45.76.185.158 2001:19f0:4400:63d6:5400:4ff:feff:c5db
Affected Components
Dedicated-US-CA-Los Angeles
US-CA-Los Angeles
Dedicated-US-NY-New York
EXT-TXN-Dedicated-US-NY-New York
US-NY-New York
Dedicated-Germany-Frankfurt
Germany-Frankfurt
EXT-TXN-Dedicated-Singapore-Singapore
IPv6 source address mismatch in US-DAL/LAX/HNL/ATL, CAN-TOR, FRA-PAR, JPN-OSASep 29, 2026 14:30 GMT — ongoing (1d 21h)
InvestigatingSep 29, 2026 14:30:00 GMT
We found a mismatch between the IPv6 addresses that we announced for some probe locations and the IPv6 addresses that these locations actually use for checks.
Affected locations
United States - Dallas
United States - Los Angeles
United States - Honolulu
United States - Atlanta
Canada - Toronto
France - Paris
Japan - Osaka
Impact
IPv6 checks from these locations can come from an address that is not on our published list. If your firewall or allowlist uses the published list, it can block these checks. This can cause false "down" alerts.
Workaround
Use IPv4 checks for these locations until we correct the list.
--
We are working on bringing announced IPs back to our servers.
Affected Components
US-TX-Dallas
US-CA-Los Angeles
US-HI-Honolulu
US-GA-Atlanta
France-Paris
Japan-Osaka
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning - 05 October 2026Oct 05, 2026 00:00 GMT — Oct 05, 2026 23:59 GMT (1d 0h)
Scheduled MaintenanceOct 05, 2026 00:00:00 GMT
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning - 05 October 2026
Date: October 5, 2026
Impact: No monitoring downtime. Action may be required if you allowlist our probe IPs.
What is happening
As part of ongoing infrastructure improvements, on October 5, 2026 we are retiring a set of legacy checking node IP addresses across several probe locations. Monitoring from these locations continues without interruption from replacement addresses.
Which customers are affected
Only customers who allowlist (whitelist) our probe IP addresses on firewalls, WAFs, CDNs, or origin servers are affected.
If you do not filter traffic by source IP, no action is needed.
Action required
Remove the addresses listed below from your allowlists.
IP addresses being decommissioned
Location	Addresses
India - Bangalore	139.59.9.12
2400:6180:100:d0::2bf:8001
139.84.139.124
2401:c080:3000:25d6:5400:04ff:fe5e:b4e6
139.84.137.94
2401:c080:3000:45ab:5400:04ff:feff:c554
France - Paris	107.155.114.50
2604:8380:2500:7::4
107.155.114.98
2604:8380:2500:9::4
Mexico - Mexico City	216.238.74.231
2001:19f0:b400:1a0c:5400:03ff:fee5:c7ad
216.238.77.144
2001:19f0:b400:1ec0:5400:04ff:fe5e:b3c6
216.238.67.86
2001:19f0:b400:25d6:5400:04ff:feff:c5a1
USA - Honolulu, HI	208.83.232.50
2001:19f0:c000:c6f7:5400:04ff:fe96:7338
USA - San Jose, CA	169.150.221.220
2a02:6ea0:e610::2
144.202.101.196
2001:19f0:ac00:474d:5400:04ff:feff:c65e
United Kingdom - London	5.180.211.91
2a0d:5082:0:5::2
5.180.211.92
2a0d:5082:0:8::2
5.180.211.97
2a0d:5082:0:b::2
5.180.211.98
2a0d:5082:0:c::2
5.180.210.177
2a0d:5082:0:18::2
185.245.80.150
2a0d:5082:0:14::2
78.141.198.212
2001:19f0:7402:2ce:5400:04ff:fe5e:b38f
209.250.228.103
2001:19f0:7400:2d92:5400:04ff:feff:c5e2
Argentina - Buenos Aires	200.25.62.84
2800:1e0:1030:2::14
Indonesia - Jakarta	129.227.33.182
2602:ffe4:c0d:4002::2
Philippines - Manila	128.1.209.242
2602:ffe4:c06:408a::2
Saudi Arabia - Riyadh	8.213.82.50
240b:400c:118:9900:dea8:c7b9:ec9e:5863
Questions
If you need help updating your allowlists, contact [email protected] and we will assist.
Plain-text copy of all decommissioned addresses
139.59.9.12 139.84.139.124 139.84.137.94 2400:6180:100:d0::2bf:8001 2401:c080:3000:25d6:5400:04ff:fe5e:b4e6 2401:c080:3000:45ab:5400:04ff:feff:c554 107.155.114.50 107.155.114.98 2604:8380:2500:7::4 2604:8380:2500:9::4 216.238.74.231 216.238.77.144 216.238.67.86 2001:19f0:b400:1a0c:5400:03ff:fee5:c7ad 2001:19f0:b400:1ec0:5400:04ff:fe5e:b3c6 2001:19f0:b400:25d6:5400:04ff:feff:c5a1 208.83.232.50 2001:19f0:c000:c6f7:5400:04ff:fe96:7338 169.150.221.220 144.202.101.196 2a02:6ea0:e610::2 2001:19f0:ac00:474d:5400:04ff:feff:c65e 5.180.211.91 5.180.211.92 5.180.211.97 5.180.211.98 5.180.210.177 185.245.80.150 78.141.198.212 209.250.228.103 2a0d:5082:0:5::2 2a0d:5082:0:8::2 2a0d:5082:0:b::2 2a0d:5082:0:c::2 2a0d:5082:0:18::2 2a0d:5082:0:14::2 2001:19f0:7402:2ce:5400:04ff:fe5e:b38f 2001:19f0:7400:2d92:5400:04ff:feff:c5e2 200.25.62.84 2800:1e0:1030:2::14 129.227.33.182 2602:ffe4:c0d:4002::2 128.1.209.242 2602:ffe4:c06:408a::2 8.213.82.50 240b:400c:118:9900:dea8:c7b9:ec9e:5863
Affected Components
EXT-TXN-Dedicated-India-Bangalore
India-Bangalore
France-Paris
Dedicated-Mexico-Mexico City
EXT-TXN-Dedicated-Mexico-Mexico City
Mexico-Mexico City
US-HI-Honolulu
EXT-TXN-Dedicated-US-CA-San Jose
US-CA-San Jose
EXT-TXN-Dedicated-United Kingdom-London
Dedicated-United Kingdom-London
United Kingdom-London
Argentina-Buenos Aires
Indonesia-Jakarta
Philippines-Manila
Saudi Arabia-Riyadh
Dedicated-India-Bangalore
Global Probe Server Expansion (5 October 2026)Oct 05, 2026 13:35 GMT — Oct 05, 2026 23:59 GMT (10h 25m)
Scheduled MaintenanceOct 05, 2026 13:35:00 GMT
Probe Network Update: New Location and IP Address Changes
To improve monitoring reliability, we are adding a new probe location in Dublin, Ireland and moving our Toronto, Milan and Bogotá probes to new infrastructure. The locations moving to new infrastructure will send checks from new IP addresses, and the old addresses will be retired.
Timeline
On Monday, 5 October 2026:
The new endpoints below join the active monitoring pool.
The old Toronto and Milan addresses are retired and stop sending traffic.
Action Required: Firewall & ACL Updates
If your environment restricts inbound traffic, add the new IPv4 and IPv6 addresses below to your firewalls or Access Control Lists (ACLs) before 5 October 2026. Adding them early prevents false-positive alerts and keeps your monitoring running without interruption.
New Probe Endpoints
Location	IPv4	IPv6
Ireland (Dublin) — New	185.34.0.131	2a00:dd80:d:8::6
Canada (Toronto)	155.138.147.240	2001:19f0:b002:2c1:5400:6ff:fec1:aa42
Italy (Milan)	172.232.205.147	2600:3c0b:e001:91::1
Colombia (Bogotá)	148.163.225.5	2607:f740:111:1::2e
Retiring Probe Endpoints
These addresses stop sending traffic on 5 October 2026. After that date, you can safely remove them from your allowlists.
Location	IPv4	IPv6
Canada (Toronto)	162.248.221.15	2607:f740:50::c
Italy (Milan)	66.245.212.201	2a05:f480:3800:13a3:5400:6ff:fe75:a9b6
Note: Add the new addresses to your existing allowlists rather than replacing them. Keep the retiring addresses until 5 October 2026 so monitoring isn't interrupted during the switch.
If you have any questions or need help, please contact our support team.
Affected Components
Ireland-Dublin
EXT-TXN-Dedicated-Canada-Toronto
Dedicated-Canada-Toronto
Canada-Toronto
Italy-Milan
Colombia-Bogota
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning - 01 October 2026Oct 01, 2026 00:00 GMT — Oct 01, 2026 23:59 GMT (1d 0h)
Scheduled MaintenanceOct 01, 2026 00:00:00 GMT
Post Maintenance: Global Probe Server Expansion, Monitoring IP Address Decommissioning - 01 October 2026
Date: October 1, 2026
Impact: No monitoring downtime. Action may be required if you allowlist our probe IPs.
What is happening
As part of ongoing infrastructure improvements, on October 1, 2026 we are retiring a set of legacy checking node IP addresses across several probe locations. Monitoring from these locations continues without interruption from replacement addresses.
Which customers are affected
Only customers who allowlist (whitelist) our probe IP addresses on firewalls, WAFs, CDNs, or origin servers are affected.
If you do not filter traffic by source IP, no action is needed.
Action required
Remove the addresses listed below from your allowlists.
IP addresses being decommissioned
Location	Addresses
USA - Dallas, TX	2.56.188.133
2a0b:f302:2:7::2
2.56.188.139
2a0b:f302:2:8::2
2.56.188.158
2a0b:f302:2:9::2
2.56.188.159
2a0b:f302:2:a::2
2.56.188.161
2a0b:f302:2:6::2
2.56.188.143
2a0b:f302:2:4::2
2.56.188.172
2a0b:f302:2:b::2
2.56.188.217
2a0b:f302:2:5::2
2.56.188.194
2a0b:f302:2:10::2
Canada - Montreal	107.161.66.164
2607:f748:1200:11f::4
107.161.66.165
2607:f748:1200:11f::5
China - Hong Kong	64.120.114.163
2402:a7c1:2010:a00b:4::4
Poland - Warsaw	45.159.98.131
2a00:dd80:40:100::2ca
United Arab Emirates - Dubai	176.125.231.82
2001:ac8:81:50::2
USA - Denver, CO	121.127.44.74
2a02:6ea0:d70e::2
USA - Miami, FL	195.181.163.168
2a02:6ea0:cc35::2
USA - Kansas City, MO	104.225.19.237
2607:f740:75:1::3d4
Questions
If you need help updating your allowlists, contact [email protected] and we will assist.
Plain-text copy of all decommissioned addresses
2.56.188.133 2.56.188.139 2.56.188.158 2.56.188.159 2.56.188.161 2.56.188.143 2.56.188.172 2.56.188.217 2.56.188.194 2a0b:f302:2:7::2 2a0b:f302:2:8::2 2a0b:f302:2:9::2 2a0b:f302:2:a::2 2a0b:f302:2:6::2 2a0b:f302:2:4::2 2a0b:f302:2:b::2 2a0b:f302:2:5::2 2a0b:f302:2:10::2 107.161.66.164 107.161.66.165 2607:f748:1200:11f::4 2607:f748:1200:11f::5 64.120.114.163 2402:a7c1:2010:a00b:4::4 45.159.98.131 2a00:dd80:40:100::2ca 176.125.231.82 2001:ac8:81:50::2 121.127.44.74 2a02:6ea0:d70e::2 195.181.163.168 2a02:6ea0:cc35::2 104.225.19.237 2607:f740:75:1::3d4
Affected Components
US-TX-Dallas
Canada-Montreal
China-Hong Kong
Poland-Warsaw
United Arab Emirates-Dubai
US-CO-Denver
US-FL-Miami
US-MO-Kansas City
Components: Current Status
Name
Status
API
Operational
Background Processing
Operational
Check Servers
Partial Outage
AUTO (SingleLocationChecks)
Operational
Austria-Vienna
Operational
Argentina-Buenos Aires
Operational
Australia-Brisbane
Operational
Australia-Melbourne
Operational
Australia-Perth
Operational
Australia-Sydney
Partial Outage
Belgium-Brussels
Operational
Bolivia-La Paz
Operational
Brazil-Brasília
Operational
Brazil-Sao Paulo
Operational
Bulgaria-Sofia
Operational
Canada-Montreal
Operational
Canada-Toronto
Operational
Canada-Vancouver
Operational
Chile-Santiago
Operational
China-Hong Kong
Operational
Colombia-Bogota
Operational
Denmark-Copenhagen
Operational
Finland-Helsinki
Operational
France-Paris
Partial Outage
Germany-Berlin
Operational
Germany-Frankfurt
Operational
Germany-Munich
Operational
Ghana-Accra
Operational
Greece-Athens
Operational
India-Bangalore
Operational
Indonesia-Jakarta
Operational
Ireland-Dublin
Operational
Israel-Tel Aviv
Operational
Italy-Milan
Operational
Japan-Osaka
Partial Outage
Japan-Tokyo
Operational
Kenya-Nairobi
Operational
Latvia-Riga
Operational
Lithuania-Vilnius
Operational
Luxembourg-Bettembourg
Operational
Malaysia-Kuala Lumpur
Operational
Mexico-Mexico City
Operational
Netherlands-Amsterdam
Operational
New Zealand-Auckland
Operational
Nigeria-Lagos
Operational
Norway-Oslo
Operational
Panama-Panama City
Operational
Peru-Lima
Operational
Philippines-Manila
Operational
Poland-Warsaw
Operational
Portugal-Lisbon
Operational
Puerto Rico-San Juan
Operational
Romania-Bucharest
Operational
Saudi Arabia-Riyadh
Operational
Serbia-Belgrade
Operational
Singapore-Singapore
Partial Outage
South Africa-Cape Town
Operational
South Africa-Johannesburg
Operational
South Korea-Seoul
Operational
Spain-Madrid
Operational
Sweden-Stockholm
Operational
Switzerland-Geneva
Operational
Switzerland-Zurich
Operational
Taiwan-Taipei
Operational
Thailand-Bangkok
Operational
Turkey-Ankara
Operational
Ukraine-Kiev
Operational
United Arab Emirates-Dubai
Operational
United Kingdom-Edinburgh
Operational
United Kingdom-London
Operational
United Kingdom-Manchester
Operational
United Kingdom-Portsmouth
Operational
United Kingdom-Wolverhampton
Operational
US-CA-Los Angeles
Partial Outage
US-NY-New York
Operational
US-TX-Dallas
Partial Outage
US-CA-Fremont
Operational
US-CA-San Francisco
Operational
US-CA-San Jose
Operational
US-CO-Denver
Operational
US-FL-Miami
Operational
US-GA-Atlanta
Partial Outage
US-HI-Honolulu
Partial Outage
US-IL-Chicago
Operational
US-MA-Boston
Operational
US-MO-Kansas City
Operational
US-NV-Las Vegas
Operational
US-UT-Ogden
Operational
US-VA-Manassas
Operational
US-WA-Seattle
Operational
Vietnam-Hanoi
Operational
Extended Transaction Check Servers
Operational
EXT-TXN-Dedicated-Canada-Toronto
Operational
EXT-TXN-Dedicated-India-Bangalore
Operational
EXT-TXN-Dedicated-Mexico-Mexico City
Operational
EXT-TXN-Dedicated-Singapore-Singapore
Operational
EXT-TXN-Dedicated-United Kingdom-London
Operational
EXT-TXN-Dedicated-US-CA-San Jose
Operational
EXT-TXN-Dedicated-US-NY-New York
Operational
Freetools Check Servers
Operational
Freetools-Australia-Sydney
Operational
Freetools-Germany-Frankfurt
Operational
Freetools-US-NY-New York
Operational
Page Speed Check Servers
Operational
Dedicated-Brazil-Brasília
Operational
Dedicated-Brazil-Sao Paulo
Operational
Dedicated-Canada-Toronto
Operational
Dedicated-Germany-Frankfurt
Operational
Dedicated-India-Bangalore
Operational
Dedicated-Mexico-Mexico City
Operational
Dedicated-Portugal-Lisbon
Operational
Dedicated-Singapore-Singapore
Operational
Dedicated-United Kingdom-London
Operational
Dedicated-US-CA-Los Angeles
Operational
Dedicated-US-NY-New York
Operational
Database
Operational
Documentation/Support
Operational
Login & SSO
Operational
Metrics Database
Operational
Mobile Application
Operational
Notification Delivery
Operational
SMS
Operational
Voice
Operational
Email
Operational
Push Notifications
Operational
Real User Monitoring
Operational
Integrations
Operational
Status Pages
Operational
Web Application
Operational
Website
Operational
Checks
Operational
Secure Vault
Partial Outage
Powered by Uptime.com Status Page
Today
Yesterday
Last 7 Days
Last 30 Days
This Month
Last Month
This Year
Last Year
Custom Range