bgpreport

Network · data from 2026-11-12

AS199122 ECHA-AS European Chemicals Agency

Registry name: ECHA-AS European Chemicals Agency, FI · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
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
1Route objects not announced registered with origin AS199122, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199122, 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.
57.86.147.16/28 Invalid: origin None 2 0%low visibility 2

AS-SET

AS199122 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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin57.86.147.16/28ROAs covering it name AS2874, AS51964, not AS199122. If AS199122 should announce it, add a ROA for AS199122.2 of 673
Route object: none57.86.147.16/28No route object for it. Add a route object with origin AS199122 in the RIR database for the space.2 of 673

Route objects not announced

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

194.187.232.0/22RIPENo 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.