Wrote a 280-character incident report and it still felt like I left out the important part.
Iris Veldhuis
If it fits in 280 characters I might be wrong, but I will be brief.
That matches what I saw. Timestamp even lines up. [52.1]
Update 114: Espresso in Zwolle tasted like someone finally cleaned the group head. Small civic miracle.
That matches what I saw. Timestamp even lines up. [27.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [52.2]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [27.2]
Update 115: The construction on the way to Maastricht has entered its third personality. Today it is a labyrinth.
Do you have a ticket number? The public status page is lagging again. [52.3]
Do you have a ticket number? The public status page is lagging again. [27.3]
I can bring a folding table if we are still on for Weesp. [52.4]
The 07:12 to Filmwijk was on time. I do not know how to process this emotionally.
Update 116: Self-hosting update: the backup ran. The restore drill did not. Guess what I am doing tonight.
Stopped using a CDN in front of a static site. Latency went up, bills and mystery headers went down.
On it. I will check the probe from Rotterdam Blaak when I am home. [13.1]
Found a bench in Lelystad that is not next to a speaker. I am not telling you which one.
Not sure this belongs in a public space, but the technical bit is fair. [13.2]
Work identity thought of the day: private spaces should leak nothing. Not even the joke.
Seconded. Also: hydrate. You sound like you have been in DNS for six hours. [13.3]
I had the opposite experience in Bussum. Maybe it is a platform thing. [13.4]