bgpreport

Network · data from 2026-11-12

AS8414 International Telecommunication Union

Registry name: International Telecommunication Union, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8414, 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.
2a00:7580:60::/48 No ROA RIR databaseRIPE 634 100% 67
156.106.251.0/24 Valid Nonecovered by 156.106.128.0/17 672 100% 67
156.106.0.0/16 Valid RIR databaseRIPE 672 100% 67
156.106.0.0/17 Valid RIR databaseRIPE 670 100% 67
156.106.128.0/17 Valid RIR databaseRIPE 670 100% 67
193.5.62.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS8414 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: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a00:7580:60::/48No ROA covers it. Add a ROA for AS8414, maxLength 48.634 of 636
Route object: none156.106.251.0/24No route object for it. A route object for 156.106.128.0/17 with origin AS8414 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8414 in the RIR database for the space.672 of 673

Route objects not announced

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

156.106.255.0/24RIPEValid
2001:1702:14::/48RIPEInvalid: origin

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.