bgpreport

Network · data from 2026-11-12

AS28447 ONFIBER SA DE CV

Registry name: AS28447 - ONFIBER SA DE CV, MX · PeeringDB

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

Announced routes

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

38.158.203.0/24 No ROA Other origin onlycovered by 38.158.202.0/23 670 100% 66
38.158.202.0/23 No ROA Other IRR onlyRADB 671 100% 66
38.158.202.0/24 No ROA Other IRR onlyRADB 670 100% 66
38.226.104.0/24 No ROA Other IRR onlyRADB 670 100% 66
203.142.5.0/24 Valid RIR databaseLACNIC 671 100% 66
200.76.116.0/24 Valid RIR databaseLACNIC 670 100% 66
200.76.118.0/24 Valid RIR databaseLACNIC, RADB 670 100% 66
2806:3f6::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS28447: AS28447:AS-PEERS. 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 (AS28447 isn't in the set, or no route object for AS28447 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 objectsAS28447 in itNot covered
AS28447:AS-PEERS LACNIC 117 Yes 0

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

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none38.158.203.0/24No ROA covers it. Add a ROA for AS28447, maxLength 24.670 of 673
Route object: none38.158.203.0/24Route objects for it name AS28477. A route object for 38.158.202.0/23 with origin AS28447 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28447 in the RIR database for the space.670 of 673
ROA: none38.158.202.0/23No ROA covers it. Add a ROA for AS28447, maxLength 23.671 of 673
Route object: RIR38.158.202.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.158.202.0/24No ROA covers it. Add a ROA for AS28447, maxLength 24.670 of 673
Route object: RIR38.158.202.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.226.104.0/24No ROA covers it. Add a ROA for AS28447, maxLength 24.670 of 673
Route object: RIR38.226.104.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS28447 is announced.

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.