bgpreport

Network · data from 2026-11-12

AS52209 LordVPS

Registry name: LORDVPSNLNETWORKNL Atis Omran Sevin PSJ, IR · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS52209, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52209, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
5.63.23.0/24 Valid RIR databaseRIPE 668 99% 67
80.244.11.0/24 Valid RIR databaseRIPE 662 98% 67

AS-SET

AS52209's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • Route object: not announced14

Route objects not announced

Route objects with origin AS52209 whose prefix no peer sees AS52209 announce. Many are kept on purpose (backup routes, space announced only in some places).

89.46.24.0/21RIPEValid
91.239.189.0/24RIPEValid
185.154.190.0/24RIPEValid
194.5.54.0/24RIPEValid
2a09:a6c0::/29RIPEValid
2a09:cbc0::/29RIPEValid
2a13:1640::/29RIPEValid
2a13:3cc0::/29RIPEInvalid: origin
2a13:6340::/29RIPEInvalid: origin
2a13:6fc0::/29RIPEInvalid: origin
2a13:9600::/29RIPEValid
2a13:9a00::/29RIPEValid
2a13:9dc0::/29RIPEValid
2a13:9e40::/29RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.