Some service information could not be verified. This is the last known report, not an all-clear.
Incident history
November
4 NovRailway advisory: US East public networkingResolved
Railway reports a disruption to US East public networking. Provider source: https://status.railway.com/. This is an upstream advisory. Impact on individual VidCC requests has not been confirmed.
Timeline and report
- ResolvedLatest update
The affected upstream components reported operational status on three consecutive checks. This closes the provider advisory, not a claim that every VidCC request was affected.
- Investigating
Railway reports a disruption to US East public networking. Provider source: https://status.railway.com/. This is an upstream advisory. Impact on individual VidCC requests has not been confirmed.
October
13 OctVidCC readiness checks failingResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 6 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 OctVidCC web availabilityResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 6 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 OctAnalysis processing unavailableResolved
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 6 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
4 OctVidCC web availabilityResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 8 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
4 OctAnalysis processing unavailableResolved
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 8 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
4 OctVidCC readiness checks failingResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 8 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
September
30 SeptRailway advisory: US East public networkingResolved
Railway reports a disruption to US East public networking. Provider source: https://status.railway.com/. This is an upstream advisory. Impact on individual VidCC requests has not been confirmed.
Timeline and report
- ResolvedLatest update
The affected upstream components reported operational status on three consecutive checks. This closes the provider advisory, not a claim that every VidCC request was affected.
- Investigating
Railway reports a disruption to US East public networking. Provider source: https://status.railway.com/. This is an upstream advisory. Impact on individual VidCC requests has not been confirmed.
29 SeptVidCC readiness checks failingResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 10 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
28 SeptVidCC application and database updateResolved
VidCC will be temporarily unavailable while we update the application and database. We’ll post an update when service is restored.
Timeline and report
- ResolvedLatest update
The planned window has ended and the required availability checks passed three consecutive times. Recovery was confirmed at 2026-09-28T23:29:49.535Z. The maintenance window is not a measurement of continuous customer downtime.
- Identified
The scheduled maintenance window has started. Expected end: 2026-09-28T23:27:00.000Z. This is a planned interruption notice, not a measurement of downtime. Recovery will be checked automatically.
27 SeptVidCC readiness checks failingResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
27 SeptVidCC web availabilityResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
27 SeptAnalysis processing unavailableResolved
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 SeptAnalysis processing unavailableResolved
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's analysis worker health check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 SeptVidCC readiness checks failingResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 SeptVidCC web availabilityResolved
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
Timeline and report
- ResolvedLatest update
Three consecutive checks passed. The observed incident window was approximately 5 minutes, including the recovery confirmation period. These are sampled availability checks; the root cause and individual customer impact have not been established.
- Investigating
VidCC's public availability check did not pass. Three consecutive checks failed. The cause has not been confirmed.
13 SeptScheduled database updateResolved
VidCC will be briefly unavailable while we complete a database update. We’ll confirm here when service is restored.
Timeline and report
- ResolvedLatest update
The planned window has ended and the required availability checks passed three consecutive times. Recovery was confirmed at 2026-09-13T22:28:33.791Z. The maintenance window is not a measurement of continuous customer downtime.
- Identified
The scheduled maintenance window has started. Expected end: 2026-09-13T22:25:47Z. This is a planned interruption notice, not a measurement of downtime. Recovery will be checked automatically.
12 SeptUS East infrastructure maintenanceResolved
Scheduled maintenance on 12 September 2026 is complete. VidCC services were briefly unavailable during the 12:25 to 12:40 UTC maintenance window. Normal service has been restored.
Timeline and report
- ResolvedLatest update
Maintenance is complete. All services have been checked and are operating normally.
- Resolved
Services were briefly unavailable during scheduled maintenance. Service checks confirmed recovery at 12:32 UTC, and final checks were completed before the maintenance window ended at 12:40 UTC.