bgpreport

Network · data from 2026-11-12

AS47201 AEDAAS1 TELECOMMUNICATIONS AND DIGITAL GOVERNMENT REGULATORY AUTHORITY

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

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
8Route objects not announced registered with origin AS47201, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47201, 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.
79.98.120.0/24 Valid Other IRR onlyRADB 673 100% 67
79.98.121.0/24 Valid Other IRR onlyRADB 673 100% 67
79.98.124.0/24 Valid Other IRR onlyRADB 673 100% 67
79.98.125.0/24 Valid Other IRR onlyRADB 673 100% 67
2a00:d30:120::/48 Valid Other IRR onlyRADB 634 100% 68
2a00:d30:121::/48 Valid Other IRR onlyRADB 634 100% 68
2a00:d30:124::/48 Valid Other IRR onlyRADB 634 100% 68
2a00:d30:125::/48 Valid Other IRR onlyRADB 634 100% 68

AS-SET

AS47201 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 16 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR79.98.120.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR79.98.121.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR79.98.124.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR79.98.125.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2a00:d30:120::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2a00:d30:121::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2a00:d30:124::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2a00:d30:125::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

79.98.120.0/23RIPENo ROA
79.98.122.0/23RIPENo ROA
79.98.122.0/24RADBValid
79.98.123.0/24RADBValid
79.98.124.0/23RIPENo ROA
2a00:d30::/32RIPENo ROA
2a00:d30:122::/48RADBValid
2a00:d30:123::/48RADBValid

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.