Daily’s incident blames AWS as the cause. (hop 1, posted +0 min vs the first vendor naming AWS)
“…e resolved. We're continuing to see issues across our platform as a result of the ongoing AWS outage. You'll likely experience problems joining calls, accessing the Dashboard, or using the REST API. W…”
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
What changed
Struck in red is what Daily removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Connectivity issues
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2021-12-15 15:32 UTC
AddedResolved time#5
Before: not present
After: 2021-12-15 16:35 UTC
AddedAffected components#6
Before: not present
After: API, Core Call Experience, Dashboard, Media Services, Recording/Live Streaming
AddedUpdateinvestigating#7
Before: not present
After: We're investigating reports of problems connecting to calls.
AddedUpdateidentified#8
Before: not present
After: We're experiencing network delays and timeouts throughout our infrastructure as a result of a larger-scale AWS incident. You may experience problems connecting to calls, viewing your Dashboard, or making REST API requests. We'll update this incident as we know more.
AddedUpdateidentified#9
Before: not present
After: We're continuing to see issues across our platform as a result of the ongoing AWS outage. You'll likely experience problems joining calls, accessing the Dashboard, or using the REST API. We'll continue to post more information here as we have it.
AddedUpdateidentified#10
Before: not present
After: We've seen overall error rates decrease as AWS has been working to resolve the networking issue. Things are improving, but you may still experience delays and errors until this issue is fully resolved.
AddedUpdateresolved#11
Before: not present
After: Error rates and network metrics have returned to normal levels, so we're considering this issue resolved.