Loading
Applying language and content...
Loading status page
Checking service and reports...
47 Runrunit incidents · 2014년 6월 — official updates, affected components, duration and resolution details.
We are currently investigating this issue.
This incident has been resolved.
Some of our servers are experiencing instability at this moment. The technical team is already investigating.
We are currently investigating this issue
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We're having trouble with webhook notifications. Reporting and real-time updates can be compromised. We are in contact with our infrastructure provider looking for alternatives.
This incident has been resolved.
We are currently investigating this issue
The issue has been identified and fix is being implemented
A fix has been implemented and we are monitoring the results
We are continuing to monitor for any further issues.
This incident has been resolved.
Investigating - Technical Team investigating
We are continuing to investigate this issue.
This incident has been resolved.
Investigating - Technical Team investigating
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Investigating - Unstable Servers. Technical Team investigating
This incident has been resolved.
Investigating - Unstable Servers. Technical Team investigating
Our hosting provider, Google Cloud, is experiencing a routing outage. Google Cloud Status: https://status.cloud.google.com/
We are continuing to investigate this issue.
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
This incident has been resolved.
Investigating - Technical team investigating.
We are continuing to investigate this issue.
We are experiencing a slowdown caused by a problem in one of the components of our network infrastructure at Google. Google engineers are working on the solution to our network layer's slowness. The incident started around 13:50 (UTC -03:00). There was a performance improvement around 16:30 (UTC -03:00) but we are still below our normal performance.
During investigation we found that the problem appears to be caused by the internet service provider (ISP). Packet loss is happening on the way to our servers. The problem seems to be concentrated in VIVO users and other providers that make use of its infrastructure. Our metrics show that the network returned to normal levels around 21:00 (UTC -03:00).
This incident has been resolved.
DB maintenance
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
We are continuing to investigate this issue.
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
We are continuing to investigate this issue.
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
We are continuing to investigate this issue. An internal problem with Google’s infrastructure is preventing access to our servers. Google status page (https://status.cloud.google.com/)
We are continuing to investigate this issue.
The Google infrastructure problem has been resolved and access to Runrun.it has been re-established. It is still expected a greater delay in reporting due to the large amount of requests
This incident has been resolved.
Investigating - Unstable servers. Technical team investigating.
This incident has been resolved.