bgpreport

Network · data from 2026-11-12

AS263444 Open X Tecnologia Ltda

Registry name: AS263444 - Open X Tecnologia Ltda, BR · PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
3Route objects not announced registered with origin AS263444, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263444, 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.
138.36.164.0/24 Valid Other IRR onlyRADB 672 100% 66
138.36.167.0/24 Valid Other IRR onlyRADB 672 100% 67
177.91.160.0/22 Valid Other IRR onlyRADB 672 100% 66
177.91.160.0/23 Valid Other IRR onlyRADB 672 100% 66
177.91.161.0/24 Valid Other IRR onlyRADB 672 100% 66
177.91.162.0/23 Valid Other IRR onlyRADB 672 100% 66
177.91.163.0/24 Valid Other IRR onlyRADB 672 100% 66
138.36.165.0/24 Valid Other IRR onlyRADB 671 100% 66
177.91.160.0/24 Valid Other IRR onlyRADB 671 100% 66
177.91.162.0/24 Valid Other IRR onlyRADB 671 100% 66
2804:11dc:7000::/36 Valid Other IRR onlyRADB 636 100% 67
2804:11dc::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:1000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:2000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:4000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:8000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:a000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:11dc:e000::/36 Valid Other IRR onlyRADB 635 100% 67
64.52.14.0/24 Valid RIR databaseARIN, RADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS263444: AS-OPENX. 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 (AS263444 isn't in the set, or no route object for AS263444 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 objectsAS263444 in itNot covered
AS-OPENX RADB 3,14814117,664 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 21 are in fix.csv.

  • Route object: RIR18
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR138.36.164.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.167.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.160.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.160.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.162.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.163.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.36.165.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.91.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.91.162.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:11dc:7000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:11dc::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:1000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:8000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:a000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:11dc:e000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

138.36.164.0/22RADBValid
2804:11dc::/32RADBNo ROA
2804:11dc:6000::/36RADBNo 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.