bgpreport

Network · data from 2026-11-12

AS272694 ONEX DATA CENTERS LTDA

Registry name: AS272694 - ONEX DATA CENTERS LTDA, BR · PeeringDB

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

Announced routes

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

2804:8730::/34 No ROA Nonecovered by 2804:8730::/32 349 55% 64
2804:8730:4000::/34 No ROA Nonecovered by 2804:8730::/32 349 55% 64
2804:8730:8000::/34 No ROA Nonecovered by 2804:8730::/32 349 55% 64
2804:8730:c000::/34 No ROA Nonecovered by 2804:8730::/32 349 55% 64
149.57.32.0/23 No ROA Other IRR onlyRADB 672 100% 66
149.57.32.0/24 No ROA Other IRR onlyRADB 672 100% 66
149.57.33.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.6.119.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:8730::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS272694: AS272694. 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 (AS272694 isn't in the set, or no route object for AS272694 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 objectsAS272694 in itNot covered
AS272694 A single AS number, not a set: AS272694 (this network), 9 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 22 are in fix.csv.

  • ROA: none9
  • Route object: none4
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:8730::/34No ROA covers it. Add a ROA for AS272694, maxLength 34.349 of 636
Route object: none2804:8730::/34No route object for it. A route object for 2804:8730::/32 with origin AS272694 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272694 in the RIR database for the space.349 of 636
ROA: none2804:8730:4000::/34No ROA covers it. Add a ROA for AS272694, maxLength 34.349 of 636
Route object: none2804:8730:4000::/34No route object for it. A route object for 2804:8730::/32 with origin AS272694 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272694 in the RIR database for the space.349 of 636
ROA: none2804:8730:8000::/34No ROA covers it. Add a ROA for AS272694, maxLength 34.349 of 636
Route object: none2804:8730:8000::/34No route object for it. A route object for 2804:8730::/32 with origin AS272694 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272694 in the RIR database for the space.349 of 636
ROA: none2804:8730:c000::/34No ROA covers it. Add a ROA for AS272694, maxLength 34.349 of 636
Route object: none2804:8730:c000::/34No route object for it. A route object for 2804:8730::/32 with origin AS272694 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272694 in the RIR database for the space.349 of 636
ROA: none149.57.32.0/23No ROA covers it. Add a ROA for AS272694, maxLength 23.672 of 673
Route object: RIR149.57.32.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.57.32.0/24No ROA covers it. Add a ROA for AS272694, maxLength 24.672 of 673
Route object: RIR149.57.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.57.33.0/24No ROA covers it. Add a ROA for AS272694, maxLength 24.672 of 673
Route object: RIR149.57.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.6.119.0/24No ROA covers it. Add a ROA for AS272694, maxLength 24.672 of 673
Route object: RIR154.6.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:8730::/32No ROA covers it. Add a ROA for AS272694, maxLength 32.635 of 636
Route object: RIR2804:8730::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

149.18.32.0/23RADBNo ROA
149.18.32.0/24RADBNo ROA
149.18.33.0/24RADBNo ROA
154.6.151.0/24RADBNo 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.