(no title)
dave_universetf | 7 months ago
No idea if that's what's going on, but routing protocols are one of a few effectively global control planes that can go wrong very quickly like this.
dave_universetf | 7 months ago
No idea if that's what's going on, but routing protocols are one of a few effectively global control planes that can go wrong very quickly like this.
indigodaddy|7 months ago
ta1243|7 months ago
Traceroute from "the internet" back to that IP reaches AS14593 just fine, and my endpoint doesn't get beyond the first hop of the local starlink router.
Whatever it is, it doesn't look like a peering problem
dave_universetf|7 months ago
FollowingTheDao|7 months ago
oceanplexian|7 months ago
halfmatthalfcat|7 months ago
axus|7 months ago
dmonitor|7 months ago
chasd00|7 months ago
hdgvhicv|7 months ago
airspresso|7 months ago
But hey, if you haven’t caused an incident yet, that just means you’re still in onboarding. Those SLA downtime budgets are there to be spent.
hedora|7 months ago
It says it didn’t, and it says the “which way is down” thing hasn’t converged. Occasionally, the signal to noise ratio light in the app goes gray which means < 3.
It also rebooted itself.
Before the first reboot, 30% of pings went through. It’s almost like the azimuth or some other timely but cached data was corrupted.
chrisstanchak|7 months ago
airspresso|7 months ago