Saku speaks from the privileged position of an infrastructure owner. We
assume that interface connectivity is provided by L1 links, with OEO in
transit nodes as a worst case.
But the clever budget conscious among us have deployed router links over
provided MPLS based L2 services as critical infras
Has anyone reached out to them directly to ask what’s going on with the api?
-Aaron
Dec 18, 2024 at 3:36 PM by b...@uu3.net:
> Okey, my appology. They front page is up, but their API is down.
> I checked my frontend, but it gave me results from cache...
> I tried fresh query and got error.
>
>
>
On Fri, 10 Jan 2025 at 13:02, Jason Iannone wrote:
> Saku speaks from the privileged position of an infrastructure owner. We
> assume that interface connectivity is provided by L1 links, with OEO in
> transit nodes as a worst case.
>
> But the clever budget conscious among us have deployed rout
This is an automated weekly mailing describing the state of the Global
IPv4 Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to bg
We have a number of new 400G provider waves with odd flakiness that we
can't seem to sort out.
These links appear good - light levels are fine, links will be up with
working LLDP. But if we admin down / up the link on the IP side, many
of them won't come back up on their own. Our provider sees "
5 matches
Mail list logo