bgpreport

Network · data from 2026-11-12

AS202024 FEDnetAS1 TELECOMMUNICATIONS AND DIGITAL GOVERNMENT REGULATORY AUTHORITY

Registry name: FEDnetAS1 TELECOMMUNICATIONS AND DIGITAL GOVERNMENT REGULATORY AUTHORITY, AE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202024, 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.
91.74.123.0/24 Invalid: origin None 34 5%low visibility 21
185.54.17.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 67
79.98.126.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.98.127.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.54.16.0/22 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.54.16.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.54.16.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.54.18.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.54.18.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.54.19.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.12.0/22 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.12.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.12.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.13.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.14.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.14.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.141.15.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
46.31.70.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2a00:d30:16::/48 Valid RIR databaseRADB, RIPE 634 100% 68
2a00:d30:18::/48 Valid RIR databaseRADB, RIPE 634 100% 68

AS-SET

AS202024 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin91.74.123.0/24ROAs covering it name AS15802, not AS202024. If AS202024 should announce it, add a ROA for AS202024.34 of 673
Route object: none91.74.123.0/24No route object for it. Add a route object with origin AS202024 in the RIR database for the space.34 of 673

Route objects not announced

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

185.143.239.0/24RIPENo ROA
2a00:d30:20::/48RIPENo 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.