Network · data from 2026-11-12
AS267540 ITACELL TELECOM
Registry name: AS267540 - ITACELL TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267540, 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.
| 179.42.14.0/23 | Valid | Nonecovered by 179.42.12.0/22 | 666 99% |
| 179.42.12.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 201.182.219.0/24 | Valid | Other IRR onlyALTDB, TC | 670 100% |
| 201.182.216.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 666 99% |
| 2804:42f8:c000::/34 | Valid | Other IRR onlyALTDB, TC | 634 100% |
| 2804:42f8::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 629 99% |
| 2804:42f8::/33 | Valid | Other IRR onlyTC | 349 55% |
| 201.182.216.0/23 | Valid | Other IRR onlyTC | 203 30% |
AS-SET
PeeringDB's irr_as_set for AS267540: AS-267540. 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 (AS267540 isn't in the set, or no route object for AS267540 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 | AS267540 in it | Not covered |
|---|---|---|---|---|---|
| AS-267540 | ALTDB | 0 | 1 | No | 8 |
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: none1
- Route object: RIR7
- AS-SET: own ASN1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 179.42.14.0/23 | No route object for it. A route object for 179.42.12.0/22 with origin AS267540 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267540 in the RIR database for the space. |
| Route object: RIR | 179.42.12.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.219.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.216.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:42f8:c000::/34 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:42f8::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:42f8::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.216.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-267540 | AS267540 isn't in AS-267540 (ALTDB) once expanded. Add AS267540 to it. |
Route objects not announced
Route objects with origin AS267540 whose prefix no peer sees AS267540 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 201.182.216.0/24 | TC | Valid |
| 201.182.217.0/24 | TC | Valid |
| 201.182.218.0/23 | TC | Valid |
| 201.182.218.0/24 | TC | Valid |
| 2804:42f8::/34 | ALTDB, TC | Valid |
| 2804:42f8:4000::/34 | ALTDB, TC | Valid |
| 2804:42f8:8000::/33 | TC | Valid |
| 2804:42f8:8000::/34 | ALTDB, TC | 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.