bgpreport

Network · data from 2026-11-12

AS27673 AS27673 - Instituto Nacional de Estadistica Geografia e Info

Registry name: AS27673 - Instituto Nacional de Estadistica Geografia e Info, MX · not in PeeringDB

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

Announced routes

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

200.23.10.0/24 No ROA Other origin onlycovered by 200.23.8.0/22 672 100% 67
200.33.109.0/24 No ROA Other origin only 672 100% 67
200.23.10.0/29 No ROA Nonecovered by 200.23.8.0/22 1 0%low visibility 1
200.23.10.96/29 No ROA Nonecovered by 200.23.8.0/22 1 0%low visibility 1
200.23.8.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none200.23.10.0/24No ROA covers it. Add a ROA for AS27673, maxLength 24.672 of 673
Route object: none200.23.10.0/24Route objects for it name AS7673, AS8151, AS17072, AS19332. A route object for 200.23.8.0/22 with origin AS27673 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27673 in the RIR database for the space.672 of 673
ROA: none200.33.109.0/24No ROA covers it. Add a ROA for AS27673, maxLength 24.672 of 673
Route object: none200.33.109.0/24Route objects for it name AS7673, AS8151, AS18734, AS19332, AS32098. Add a route object with origin AS27673 in the RIR database for the space.672 of 673
ROA: none200.23.10.0/29No ROA covers it. Add a ROA for AS27673, maxLength 29.1 of 673
Route object: none200.23.10.0/29No route object for it. A route object for 200.23.8.0/22 with origin AS27673 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS27673 in the RIR database for the space.1 of 673
ROA: none200.23.10.96/29No ROA covers it. Add a ROA for AS27673, maxLength 29.1 of 673
Route object: none200.23.10.96/29No route object for it. A route object for 200.23.8.0/22 with origin AS27673 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS27673 in the RIR database for the space.1 of 673
ROA: none200.23.8.0/24No ROA covers it. Add a ROA for AS27673, maxLength 24.672 of 673
Route object: RIR200.23.8.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 AS27673 whose prefix no peer sees AS27673 announce. Many are kept on purpose (backup routes, space announced only in some places).

200.23.8.0/22RADBNo 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.