bgpreport

Network · data from 2026-11-12

AS210480 MDI Projekt MDI Sp. z o.o.

Registry name: MDI Projekt MDI Sp. z o.o., PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210480, 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.
2001:67c:8bc::/48 No ROA RIR databaseRIPE 24 4%low visibility 24

AS-SET

AS210480 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • ROA: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:8bc::/48No ROA covers it. Add a ROA for AS210480, maxLength 48.24 of 636

Route objects not announced

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

2a10:f781::/32RIPENo ROA
2a10:f781::/64RIPENo ROA
2a10:f781:0:1::/64RIPENo ROA
2a10:f781:0:ff::/64RIPENo ROA
2a10:f781:10:4912::/64RIPENo ROA
2a10:f781:10:e9c4::/64RIPENo ROA

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.