Company Logo

Is there an Test IO outage?

Test IO status: Systems Active

Last checked: 12 minutes ago

Get notified about any outages, downtime or incidents for Test IO and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Test IO outages and incidents

Outage and incident data over the last 30 days for Test IO.

There have been 0 outages or incidents for Test IO in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Test IO

Outlogger tracks the status of these components for Xero:

APIs Active
Bug Exporter Active
Cirro Active
Customer Interface Active
EWORK Active
Intercom Email Active
Intercom Intercom APIs Active
Invitation System Active
Teamleader Interface Active
Tester Interface Active
Website Active
Component Status
APIs Active
Bug Exporter Active
Cirro Active
Customer Interface Active
EWORK Active
Intercom Email Active
Intercom Intercom APIs Active
Invitation System Active
Teamleader Interface Active
Tester Interface Active
Website Active

Latest Test IO outages and incidents.

View the latest incidents for Test IO and check for official updates:

Updates:

  • Time: July 17, 2020, 10:39 p.m.
    Status: Resolved
    Update: After Cloudflare deployed their fix we are considering this issue resolved.
  • Time: July 17, 2020, 10:13 p.m.
    Status: Monitoring
    Update: Cloudflare announced having fixed the issue and to be monitoring the situation: "This afternoon we saw an outage across some parts of our network. It was not as a result of an attack. It appears a router on our global backbone announced bad routes and caused some potions of the network to not be available. We believe we have addressed the root cause and monitoring systems for stability now." - https://www.cloudflarestatus.com/
  • Time: July 17, 2020, 10:08 p.m.
    Status: Identified
    Update: Cloudflare has apparently identified the issue and is deploying a fix.
  • Time: July 17, 2020, 9:54 p.m.
    Status: Investigating
    Update: We are affected by the partial Cloudflare DNS outage and are monitoring the situation.

Updates:

  • Time: Oct. 18, 2018, 5:38 p.m.
    Status: Resolved
    Update: Everything should be back to normal.
  • Time: Oct. 18, 2018, 5:32 p.m.
    Status: Identified
    Update: Because of a faulty deployment bug details pages are not accessible, the fix is on its way.

Updates:

  • Time: May 24, 2018, 9:51 a.m.
    Status: Resolved
    Update: There was a power outage at our server provider. We apologise for the incident.
  • Time: May 24, 2018, 9:30 a.m.
    Status: Identified
    Update: Our provider identified network problems. We are working on the solution
  • Time: May 24, 2018, 9:23 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Aug. 2, 2018, 4:37 p.m.
    Status: Postmortem
    Update: #### What happened? Beginning at 2pm (UTC) on February 21st, 2018, network problems at our provider prevented test IO’s servers from properly communicating with each other. After ascertaining the reasons that the servers were not reliably reachable we took action to rectify the issue by simplifying the connection between our servers. At 6pm (UTC+1) we bypassed our load balancer by pointing the domain of our application platform directly to a single, powerful application server to ensure basic functionality of our platform. However, this led to the platform not having authorization for our content delivery network as the load balancer ensures delivery of our CORS headers. Caching of our content resulted in inconsistent outages, where some users had a functioning website but not others. Ultimately, these inconsistencies caused further frustration. Because the problem appeared fixed to those of us with the correct content already cached, we declared the problem fixed. This -- as well as our status page -- was misleading to those for whom our platform was clearly not working. Our status page is only setup to monitor the status of our servers and the ability to connect to them. Therefore it correctly displayed the 53 minutes during which our servers were truly unreachable, but not the continued intervals during which some of you were not able to access the information you wanted. #### How we fixed the problem We realized that some users were entirely blocked from our content delivery network and were not able to access Javascript and stylesheets necessary for site functionality. To fix this, at around 1am (UTC+1) on February 22nd, 2018, we centralized content sourcing directly from our main server through users’ domains, avoiding the cross-domain authorization issue. Since last night, our platform has maintained usability. To return content delivery speeds and functionality to normal, we re-enabled the load balancer and CDN at 12pm (UTC+1) on Thursday Feb 22nd, 2018. Service has since returned to the availability and reliability we know you rely on. #### Apology We strive to provide our customers, testers, and team leaders with a reliable QA testing platform, and we know that the issues with our website yesterday disrupted our customers’ business and prevented them from accomplishing their normal work. For that we sincerely apologize. In order to learn and grow from it, we are taking this opportunity to look at our current processes and improve the reliability of our service. We are currently working with our hosting provider to determine the root cause of the connectivity breakdown between our servers and investigating how we might set up our systems to fail over to another network in the event of a recurrence. We’re also looking at alternative hosting options.
  • Time: Feb. 24, 2018, 1:46 a.m.
    Status: Resolved
    Update: At 2pm (UTC) on Februrary 21st, 2018, network problems at our provider prevented test IO’s servers from properly communicating with each other. After bypassing our load-balancer issues with the CORS configuration prevented some users from using our platform. Everything is running smoothly again since 1am (UTC+1) on February 22nd, 2018.

Updates:

  • Time: Sept. 7, 2014, 10:38 p.m.
    Status: Resolved
    Update: Our monitoring confirms we are fully back online.
  • Time: Sept. 7, 2014, 10:36 p.m.
    Status: Monitoring
    Update: Everything seems to be stable again.
  • Time: Sept. 7, 2014, 10:27 p.m.
    Status: Identified
    Update: There are major network issues at our datacenter. They are working on it.
  • Time: Sept. 7, 2014, 10:08 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Check the status of similar companies and alternatives to Test IO

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Systems Active

Bandwidth
Bandwidth

Systems Active

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

LaunchDarkly
LaunchDarkly

Systems Active

Frequently Asked Questions - Test IO

Is there a Test IO outage?
The current status of Test IO is: Systems Active
Where can I find the official status page of Test IO?
The official status page for Test IO is here
How can I get notified if Test IO is down or experiencing an outage?
To get notified of any status changes to Test IO, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Test IO every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Test IO do?
Test IO provides comprehensive testing services for web, mobile, and IoT applications, offered as a convenient service.