bgpreport

Network · data from 2026-11-12

AS9827 AGILENT-AS-AP - Agilent Technologies Asia-Pacific Zone

Registry name: AGILENT-AS-AP - Agilent Technologies Asia-Pacific Zone, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9827, 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.
198.183.201.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

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

  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR198.183.201.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

141.183.0.0/16REACHNo ROA
146.208.0.0/16REACHNo ROA
146.223.0.0/16REACHNo ROA
192.25.0.0/16REACHNo ROA
192.25.46.0/24REACHNo ROA
192.25.82.0/24REACHNo 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.