Aptible’s incident blames AWS as the cause. (hop 1, posted +1 h 18 min vs the first vendor naming AWS)
“…Operations blocked - Route 53 propagation delays This incident has been resolved. This incident has been resolved. We are noticing Route 53 record requests succeeding in a normal time frame, and are l…”
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 Aptible removed; blue is what they added. Muted text is unchanged context.
After: We've noticed that some Operations are failing due to Route53 record changes not propagating within the 10 minute time limit allowed by our platform.
In order to prevent Apps and Databases DNS records from reaching an inconsistent state, we are temporarily blocking Operations.
Performance and reachability of existing Apps and Database is not impacted.
AddedUpdatemonitoring#8
Before: not present
After: We are noticing Route 53 record requests succeeding in a normal time frame, and are lifting the operation block at this time.
We'll continue to observe running operations to ensure stability.