Network · data from 2026-11-12
AS263555 Infinity Brasil telecom LTDA ME
Registry name: AS263555 - infinity brasil telecom ltda me, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263555, 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.
| 131.0.252.0/22 | Valid | Other IRR onlyALTDB, TC | 671 100% |
| 186.250.220.0/22 | Valid | Other IRR onlyALTDB, TC | 671 100% |
| 131.0.253.0/24 | Valid | Other IRR onlyALTDB | 669 99% |
| 186.250.220.0/24 | Valid | Other IRR onlyALTDB | 669 99% |
| 186.250.222.0/24 | Valid | Other IRR onlyALTDB | 669 99% |
| 2804:ee0:c000::/34 | Valid | Other IRR onlyALTDB | 634 100% |
| 2804:ee0::/32 | Valid | Other IRR onlyALTDB, TC | 632 99% |
| 2804:ee0:4000::/34 | Valid | Other IRR onlyRADB | 632 99% |
| 131.0.254.0/24 | Valid | Other IRR onlyALTDB | 207 31% |
| 131.0.255.0/24 | Valid | Other IRR onlyALTDB | 207 31% |
| 186.250.221.0/24 | Valid | Other IRR onlyALTDB | 207 31% |
| 186.250.223.0/24 | Valid | Other IRR onlyALTDB | 207 31% |
AS-SET
PeeringDB's irr_as_set for AS263555: AS-263555. 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 (AS263555 isn't in the set, or no route object for AS263555 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 | AS263555 in it | Not covered |
|---|---|---|---|---|---|
| AS-263555 | ALTDB | 1 | 1 | 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 17 are in fix.csv.
- Route object: RIR12
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.0.252.0/22 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.250.220.0/22 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.0.253.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 186.250.220.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 186.250.222.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:ee0:c000::/34 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:ee0::/32 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:ee0:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.0.254.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 131.0.255.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 186.250.221.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 186.250.223.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263555 whose prefix no peer sees AS263555 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.0.252.0/23 | ALTDB | Valid |
| 131.0.252.0/24 | ALTDB | Valid |
| 131.0.254.0/23 | ALTDB | Valid |
| 186.250.220.0/23 | ALTDB | Valid |
| 186.250.222.0/23 | ALTDB | 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.