All Systems Operational
About This Site
ClearBlade IoT Core status can be monitored and subscribed to here. Maintenance events and incidents will be tracked.
Learn more about maintenance schedules here:
https://docs.clearblade.com/iotcore/clearblade-maintenance-windows
Intelligent Assets
Operational
ClearBlade IoT Core
Operational
Administration
Operational
Europe-West1
Operational
US-Central1
Operational
Asia-East1
Operational
IoT Core Sandbox
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
IoTCore Maintenance Jun 23, 2026 12:00 - Jun 24, 2026 12:00 UTC
ClearBlade will be undergoing upgrade maintenance across all regions within their respective maintenance windows on June 23rd.
https://docs.clearblade.com/iotcore/clearblade-maintenance-windows
As part of the update, ClearBlade will update the getRegistryCredentials API to return the g5 registry URL instead of the current g1 registry URL.
The registry credentials returned by the API are not changing. Only the returned url value will change.
This update ensures customers receive the newer recommended registry endpoint and improves compatibility with modern client environments, including newer versions of Python and related MQTT/TLS libraries.
Customers who use getRegistryCredentials directly, or who use a ClearBlade SDK that calls this API, should review any devices, scripts, applications, or services that depend on the returned registry URL. If your environment uses firewall, proxy, DNS, or IP allowlists, please make sure the g5 registry endpoint is allowed before the update.
The URL changes are:
us-central1.clearblade.com -> us-central1-g5.clearblade.com
europe-west1.clearblade.com -> europe-west1-g5.clearblade.com
asia-east1.clearblade.com -> asia-east1-g5.clearblade.com
Please check the following before the update:
- Clients can connect using the g5 registry URL
- Firewalls allow outbound access to the g5 hostname
- DNS resolution is allowed for the g5 endpoint
- Proxies or TLS inspection tools do not block the connection
- Applications do not hardcode or validate against g1-only URLsCustomers already using g5 registry URLs directly may not need to make any changes.
If you have questions or need help preparing for this change, please contact ClearBlade Support before the update window.
A disconnect event is expected, and API services may be slower to respond. We will update this status page upon completion.
Posted on May 20, 2026 - 19:44 UTC
https://docs.clearblade.com/iotcore/clearblade-maintenance-windows
As part of the update, ClearBlade will update the getRegistryCredentials API to return the g5 registry URL instead of the current g1 registry URL.
The registry credentials returned by the API are not changing. Only the returned url value will change.
This update ensures customers receive the newer recommended registry endpoint and improves compatibility with modern client environments, including newer versions of Python and related MQTT/TLS libraries.
Customers who use getRegistryCredentials directly, or who use a ClearBlade SDK that calls this API, should review any devices, scripts, applications, or services that depend on the returned registry URL. If your environment uses firewall, proxy, DNS, or IP allowlists, please make sure the g5 registry endpoint is allowed before the update.
The URL changes are:
us-central1.clearblade.com -> us-central1-g5.clearblade.com
europe-west1.clearblade.com -> europe-west1-g5.clearblade.com
asia-east1.clearblade.com -> asia-east1-g5.clearblade.com
Please check the following before the update:
- Clients can connect using the g5 registry URL
- Firewalls allow outbound access to the g5 hostname
- DNS resolution is allowed for the g5 endpoint
- Proxies or TLS inspection tools do not block the connection
- Applications do not hardcode or validate against g1-only URLsCustomers already using g5 registry URLs directly may not need to make any changes.
If you have questions or need help preparing for this change, please contact ClearBlade Support before the update window.
A disconnect event is expected, and API services may be slower to respond. We will update this status page upon completion.
Posted on May 20, 2026 - 19:44 UTC