Network · data from 2026-11-12
AS265225 XINGU TELECOM LTDA
Registry name: AS265225 - XINGU TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265225, 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.
| 168.0.80.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 168.0.80.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 168.0.81.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 168.0.82.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 168.0.83.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 2804:2c88:1000::/36 | Valid | Other IRR onlyALTDB, RADB, TC | 634 100% |
| 2804:2c88::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 632 99% |
| 2804:2c88::/36 | Valid | Other IRR onlyALTDB, RADB, TC | 632 99% |
| 2804:2c88:1080::/48 | Valid | Other IRR onlyALTDB, RADB, TC | 1 0%low visibility |
| 2804:2c88:1100::/41 | Valid | Other IRR onlyALTDB, RADB, TC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS265225: AS265225. 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 (AS265225 isn't in the set, or no route object for AS265225 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 | AS265225 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS265225 | A single AS number, not a set: AS265225 (this network), 17 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 17 are in fix.csv.
- Route object: RIR10
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 168.0.80.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.80.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.81.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.82.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.83.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2c88:1000::/36 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2c88::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2c88::/36 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2c88:1080::/48 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2c88:1100::/41 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265225 whose prefix no peer sees AS265225 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.0.80.0/23 | ALTDB, RADB | Valid |
| 168.0.82.0/23 | ALTDB, RADB | Valid |
| 2804:2c88::/33 | ALTDB | Valid |
| 2804:2c88:80::/48 | ALTDB, RADB, TC | Valid |
| 2804:2c88:100::/41 | ALTDB, RADB, TC | Valid |
| 2804:2c88:8000::/33 | ALTDB, RADB | Valid |
| 2804:2c88:8000::/40 | 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.