A new simple uptime form now available to all users when creating or editing an uptime test.
• The Simple uptime form is now available to everyone. It was previously limited to a subset of users.
• When creating a new check, the Simple form is shown by default.
• When editing a check, we’ll automatically switch to the Advanced form if you’ve used any advanced options.
• Improved visibility so the Simple form is no longer shown for non-HTTP checks.
We’ve reworked the Test Overview page to make it easier to use and easier to understand, especially when something’s gone wrong.
Everything is now split into tabs
Incidents, uptime, response time, and test history all live in their own tabs.
This keeps the page cleaner and makes it quicker to find what you’re looking for.
Each section has more room, so nothing feels crammed in.
You land on the right thing by default
If a test is currently down, you’ll land straight on the Current Incident.
If it’s up, you’ll see the most recent incident instead.
No extra clicking to get to the useful stuff.
Incidents are easier to understand
Current and recent incidents show clearer details like when they started, how long they’ve been going on, status codes, response times, and where the alert came from.
You can view the response body and headers directly on the page.
Incident notes and alert details are all in one place.
Cleaner history and reporting
Archived incidents and status periods are shown in clear tables with sorting and pagination.
Test periods and latest checks are easier to scan and export if needed.
Uptime and performance are clearer
Uptime and SLA info has its own space with a simple visual overview.
Response time gets a dedicated chart so you can spot trends and slowdowns more easily.
Overall, the page is less cluttered, more focused, and gives you more useful information without getting in the way.
If you have any feedback, we'd love to hear it, just drop our support team a line!
We are happy to share a recent enhancement to our scheduled email reports, aimed at improving user experience and clarity.
What’s New?
Tidier Presentation: Scheduled email reports now feature a cleaner and more organized layout. This update ensures that you can quickly find the information you need without unnecessary clutter.
Streamlined Content: Only relevant sections will be included in the email. Sections that do not contain tests or have no current warnings/updates will be omitted. This means you will receive concise reports that focus solely on what matters most to you.
At around 9AM UTC we began to see signs that name.com services were having problems at the DNS level, with some websites using this DNS service becoming unavailable intermittently and others longer term with at this point up to 5 hours of downtime logged.
At this stage name.com has not updated their Status Page to explain the issue to users - https://status.name.com/
We expect some users of this server to receive valid outage reports that will be replicable from browser and terminal in the regions they are reported in. We are seeing these errors expressed as "Domain not found" and "Timeout/connection refused" where name.com DNS was either unable to respond to a request within a reasonable amount of time, or provided an empty or invalid response.
We will post any further updates here as the situation develops.
We are seeing an outage at Cloudflare which is affecting a currently unknown number of services. Cloudflare's own status page at https://www.cloudflarestatus.com/ has been affected for around 20 minutes, and we're seeing outages for Cloudflare customer websites, as well as tools like NPM.
UPDATE:
As of 9:30AM UTC the situation seems to be recovering.
We've made a few changes and given a fresh coat of paint to our Integrations section, here's what's different:
- The ability to filter integrations by type on the list view has been added
- A new interface has been added for integration setup, this will streamline the process for all users
- Improved UI and minor bugfixes for list view
Integrations allow you to send alerts out to a range of external providers, including Slack, Pagerduty and Pushover. This is also the section where you can configure phone-call alerts. If you haven't already - check out the integrations section in your account - and ensure you have a good set of alerting methods configured!
We will soon be launching three Multi-Location Regions for uptime testing, these will be available to all paid customers. Each region will contain 4 locations.
These regions can be utilised in cases where users wish to see confirmations from more than one location per downtime, as such we advise setting 2+ confirmation servers in test settings to ensure that this is taken advantage of.
The details for the new locations can be found below, we would advise whitelisting these new IPs:
USA REGION
NameLocationIPv4IPv6USA9Georgia66.42.84.1972001:19f0:5400:1d5b:5400:05ff:fec5:f332USA10Florida45.77.75.192001:19f0:9003:0cc3:5400:05ff:fec5:f34fUSA11New York159.89.52.2192604:a880:400:d1:0:3:3b85:9001USA12California192.241.213.1882604:a880:1:4a::c0a:b000
EUROPE REGION
NameLocationIPv4IPv6NLD5Amsterdam192.81.222.2312a03:b0c0:0:1051::1bf0:7000DEU5Frankfurt161.35.219.1582a03:b0c0:3:f0:0:1:8e81:8000GBR5London143.110.160.1612a03:b0c0:1:e0::cecb:2001FRA5Paris45.32.148.972001:19f0:6801:099e:5400:05ff:fec5:f341
ASIA REGION
NameLocationIPv4IPv6IND1Bangalore139.59.95.1432400:6180:100:d0::d038:b001SGP1Singapore152.42.203.1952400:6180:0:d2:0:2:6758:f000AUS1Sydney139.180.163.762401:c080:1800:130a:5400:05ff:fec5:f347JPN1Tokyo149.28.30.152401:c080:1000:102b:5400:05ff:fec5:f34d
We are currently experiencing access issues for users trying to log in to app, this has been identified as an issue with Cloudflare.
Monitoring and API access are unaffected and continue to work correctly. users are covered for outages and alerts.
Many Cloudflare users are affected, and users will see their Cloudflare managed sites generating downtimes through StatusCake, these are valid and will be related to Cloudflare's inability to serve the pages at current.
An outage is developing on the Azure service, Australia and some parts of Asia are currently affected. The issue is worsening and seems to have originated at around 1AM UTC on 03/11 as an intermittent problem, as of 9:30 UTC we are seeing many customers affected.
No update is available yet on Azure status page but third parties have begun to note the outage - https://azure.status.microsoft/en-gb/status
Update 12:30 UTC: The problem has not yet been acknowledged by Azure publicly but some customers are now seeing recovery of their websites.
Azure is currently experiencing a major global outage, impacting customers in multiple regions to varying degrees. Some users are reporting increased latency and degraded performance, while others are seeing complete service unavailability across various services - including Microsoft 365 and other Microsoft services, from Outlook to Minecraft.
There are widespread third-party confirmations and consistent user reports indicating issues with core Azure services. Microsoft has now acknowledged the outage on their status page.
Official Azure status updates can be found here:
🔗 https://azure.status.microsoft/en-gb/status
Impact to StatusCake:
StatusCake services remain fully operational.
We are monitoring the situation closely, but there is no direct impact to our monitoring infrastructure or uptime tests.
Azure is suffering a large global outage, this is affecting Azure customers in all regions to various degrees. With some customers having increased load time, and others seeing their sites & services completely inaccessible.
There's no first party confirmation of this outage as yet, but we are seeing strong confirmation signals from third party reports and our own users we've spoken to who have reached out to Azure.
Issues started around 8AM UTC Thursday 9th October, and persist as of 9:30AM UTC.
Official status updates from Azure can be found here - https://azure.status.microsoft/en-gb/status
Update 10:30 UTC: Azure has now updated their status page, reporting that they have experienced significant capacity loss, about 30% of Azure Front Door instances are affected, affected instances are predominantly across Europe and Africa but other regions may see problems too.
Azure confirm an estimated start time for this outage of 7:40AM UTC, unfortunately issues are still ongoing.
Details direct from Microsoft here - https://azure.status.microsoft/en-gb/status
Due to these issues and potentially related routing issues within Canada, and New York we have temporarily disabled these locations.
They will be re-enabled once Microsoft reports this problem resolved.
UPDATE - The issue has been reported as resolved by the affected providers
We’ve made it easier to choose locations when creating a test!
🌍 Select by Continent – You can now select an entire continent instead of picking individual cities. This was a much-requested feature!
✅ Simplified Selection – Each location only needs to be selected once. No more duplicate entries!
🔢 New Limit – You can now select up to 19 locations per test.
Let us know if you have any feedback – our support team is happy to help! 🚀
We're pleased to let you know that our maintenance windows feature available on all paid plans now supports putting PUSH/heartbeat checks into a maintenance state.
This means you can now emit any downtimes and alerts from these tests during periods of expected downtime.
To utilise this new function simply assign a PUSH/heartbeat check to a new or existing maintenance window where relevant.
Please feel free to reach out to our support team with any questions!
We’re glad to announce that you can now pause Push Tests on StatusCake! 🚀
Previously, once a Push Test was created, it continuously expected pushes at the defined interval. Now, with this update, you have the flexibility to pause these tests when needed.
What Does This Change Mean?
No New Test Results: When a Push Test is paused, it will stop receiving and recording new test results.
No Alerts During Pause: If a Push Test is paused, it will not trigger alerts for missing pushes, helping prevent unnecessary downtime notifications.
How to Use This Feature?
- Navigate to your Push Tests in the StatusCake dashboard.
- Locate the test you want to pause.
- Click the Pause button.
- Your test is now paused and will not receive further updates or send alerts until resumed.
To resume the test, simply click the Resume button, and monitoring will continue as usual.
We have added a new IP address for SSL monitoring, customers should add this to their whitelist if required in any firewalls or security setups:
Agent NameIP AddressSSL3162.243.140.207
This replaces the previous SSL3 IP: 104.236.163.90, which can now be removed from whitelists.
As a reminder, the Monitoring Regions upgrade will go live for paid uptime checks on Tuesday, 14th January 2025.
We encourage all customers to review the Monitoring Regions guide for a detailed explanation of how Monitoring Regions work.
Key Points:
Ensure you whitelist all IPs in your selected Monitoring Region. Smaller regions with just 4 IPs are now available for London, Amsterdam, New York, and Frankfurt.
The updated IP addresses for these smaller regions are available here.
For customers without whitelisting requirements, no action is needed.
Have questions or need assistance? Reach out to our support team anytime.
Powered by ChangeCrab