bgpreport

Network · data from 2026-11-12

AS1234 FORTUM-AS - IDDQD-AS

Registry name: FORTUM-AS - IDDQD-AS, EU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1234, 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.
132.171.0.0/16 No ROA None 673 100% 67
137.96.0.0/16 No ROA None 673 100% 67
193.110.32.0/21 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS1234 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 25 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none132.171.0.0/16No ROA covers it. Add a ROA for AS1234, maxLength 16.673 of 673
Route object: none132.171.0.0/16No route object for it. Add a route object with origin AS1234 in the RIR database for the space.673 of 673
ROA: none137.96.0.0/16No ROA covers it. Add a ROA for AS1234, maxLength 16.673 of 673
Route object: none137.96.0.0/16No route object for it. Add a route object with origin AS1234 in the RIR database for the space.673 of 673

Route objects not announced

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

1.1.2.0/24RADBNo ROA
192.176.176.0/21RIPEValid
194.110.40.0/23RIPENo ROA
202.47.64.0/20REACHInvalid: origin
202.53.224.0/19REACHInvalid: origin
202.67.8.0/21REACHInvalid: origin
202.67.32.0/20REACHNo ROA
202.78.224.0/21REACHInvalid: origin
202.87.248.0/24REACHInvalid: origin
202.92.192.0/24REACHInvalid: origin
202.93.112.0/20REACHInvalid: origin
202.122.9.0/24REACHInvalid: origin
202.122.10.0/24REACHInvalid: origin
202.123.224.0/20REACHNo ROA
202.127.96.0/20REACHInvalid: origin
202.149.66.0/24REACHInvalid: origin
202.149.72.0/24REACHInvalid: origin
202.149.73.0/24REACHInvalid: origin
202.153.224.0/19REACHInvalid: origin
202.162.208.0/22REACHNo ROA
2602:f2dc:86::/48ARINValid

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.