bgpreport

Network · data from 2026-11-12

AS32710 TELoIP

Registry name: AGNICORP-ASN - AgniCorp Inc., CA · PeeringDB

11IPv4 routes 18.2% RPKI valid · 45.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS32710, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32710, 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.

164.153.168.0/24 No ROA Nonecovered by 164.153.168.0/21 673 100% 67
164.153.169.0/24 No ROA Nonecovered by 164.153.168.0/21 673 100% 67
164.153.172.0/24 No ROA Nonecovered by 164.153.172.0/23 673 100% 67
164.153.175.0/24 No ROA Other origin onlycovered by 164.153.168.0/21 673 100% 67
164.153.177.0/24 No ROA Nonecovered by 164.153.176.0/21 673 100% 67
164.153.170.0/24 No ROA Nonecovered by 164.153.168.0/21 671 100% 67
164.153.176.0/21 No ROA Other IRR onlyRADB 673 100% 67
204.138.54.0/23 No ROA Other IRR onlyRADB 673 100% 67
204.138.56.0/22 No ROA Other IRR onlyRADB 673 100% 67
164.153.248.0/21 Valid RIR databaseARIN, RADB 673 100% 67
204.138.46.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS32710: AS32710. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS32710 isn't in the set, or no route object for AS32710 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS32710 in itNot covered
AS32710 A single AS number, not a set: AS32710 (this network), 13 route objects.

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

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none164.153.168.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.673 of 673
Route object: none164.153.168.0/24No route object for it. A route object for 164.153.168.0/21 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.673 of 673
ROA: none164.153.169.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.673 of 673
Route object: none164.153.169.0/24No route object for it. A route object for 164.153.168.0/21 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.673 of 673
ROA: none164.153.172.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.673 of 673
Route object: none164.153.172.0/24No route object for it. A route object for 164.153.172.0/23 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.673 of 673
ROA: none164.153.175.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.673 of 673
Route object: none164.153.175.0/24Route objects for it name AS16570. A route object for 164.153.168.0/21 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.673 of 673
ROA: none164.153.177.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.673 of 673
Route object: none164.153.177.0/24No route object for it. A route object for 164.153.176.0/21 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.673 of 673
ROA: none164.153.170.0/24No ROA covers it. Add a ROA for AS32710, maxLength 24.671 of 673
Route object: none164.153.170.0/24No route object for it. A route object for 164.153.168.0/21 with origin AS32710 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32710 in the RIR database for the space.671 of 673
ROA: none164.153.176.0/21No ROA covers it. Add a ROA for AS32710, maxLength 21.673 of 673
Route object: RIR164.153.176.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.138.54.0/23No ROA covers it. Add a ROA for AS32710, maxLength 23.673 of 673
Route object: RIR204.138.54.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.138.56.0/22No ROA covers it. Add a ROA for AS32710, maxLength 22.673 of 673
Route object: RIR204.138.56.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

68.179.100.0/24RADBNo ROA
164.153.165.0/24ARIN, RADBValid
164.153.168.0/21RADBNo ROA
164.153.172.0/23RADBNo ROA
164.153.173.0/24ARINValid
164.153.174.0/24RADBNo ROA
204.138.52.0/23RADBNo ROA
2605:fa00::/32RADBNo 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.