Network · data from 2026-11-12
AS263126 XMAX TELECOM
Registry name: AS263126 - XMAX TELECOM LTDA., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263126, 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.
| 177.92.184.0/22 | Valid | Other IRR onlyTC | 672 100% |
| 177.92.184.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.92.186.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.92.188.0/22 | Valid | Other IRR onlyTC | 672 100% |
| 177.92.188.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.92.190.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 2804:1724::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 177.92.184.0/21 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS263126: AS-XMAX. 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 (AS263126 isn't in the set, or no route object for AS263126 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.
| Name | Database | ASNs | Sets | AS263126 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-XMAX | In no IRR database read today. | |||||
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 13 are in fix.csv.
- Route object: RIR8
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 177.92.184.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.184.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.186.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.188.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.188.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.190.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1724::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.92.184.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS-XMAX | PeeringDB names AS-XMAX; no IRR database read has it. |
Route objects not announced
Route objects with origin AS263126 whose prefix no peer sees AS263126 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.92.184.0/24 | RADB | Valid |
| 177.92.185.0/24 | RADB | Valid |
| 177.92.186.0/24 | RADB | Valid |
| 177.92.187.0/24 | RADB | Valid |
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.