Network · data from 2026-11-12
AS53018 INTERTEM
Registry name: AS53018 - Viana & Viana Comunicacao LTDA-ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53018, 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.
| 2804:354c:4500::/40 | Valid | Nonecovered by 2804:354c::/32 | 350 55% |
| 2804:354c:8500::/40 | Valid | Nonecovered by 2804:354c::/32 | 349 55% |
| 2804:354c:8600::/40 | Valid | Nonecovered by 2804:354c::/32 | 349 55% |
| 177.72.128.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.129.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.130.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.131.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.132.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.132.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.133.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.134.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.134.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.135.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.136.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.72.130.0/23 | Valid | Other IRR onlyTC | 671 100% |
| 177.72.128.0/21 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 177.72.136.0/21 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 177.72.138.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 177.72.139.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 177.72.138.0/23 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:354c::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 177.72.128.0/22 | Valid | Other IRR onlyTC | 125 19% |
| 177.72.132.0/22 | Valid | Other IRR onlyTC | 125 19% |
| 177.72.136.0/22 | Valid | Other IRR onlyTC | 125 19% |
| 177.72.136.0/23 | Valid | Other IRR onlyTC | 125 19% |
| 177.72.140.0/22 | Valid | Other IRR onlyTC | 125 19% |
| 177.72.140.0/23 | Valid | Other IRR onlyRADB, TC | 125 19% |
| 177.72.142.0/23 | Valid | Other IRR onlyTC | 125 19% |
AS-SET
PeeringDB's irr_as_set for AS53018: AS53018:AS-INTERTELECOM. 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 (AS53018 isn't in the set, or no route object for AS53018 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 | AS53018 in it | Not covered |
|---|---|---|---|---|---|
| AS53018:AS-INTERTELECOM | TC | 1 | 3 | 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 35 are in fix.csv.
- Route object: none3
- Route object: RIR25
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:354c:4500::/40 | No route object for it. A route object for 2804:354c::/32 with origin AS53018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53018 in the RIR database for the space. |
| Route object: none | 2804:354c:8500::/40 | No route object for it. A route object for 2804:354c::/32 with origin AS53018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53018 in the RIR database for the space. |
| Route object: none | 2804:354c:8600::/40 | No route object for it. A route object for 2804:354c::/32 with origin AS53018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53018 in the RIR database for the space. |
| Route object: RIR | 177.72.128.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.129.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.130.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.131.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.132.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.132.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.133.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.134.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.134.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.135.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.136.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.130.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.128.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.136.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.138.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.139.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.138.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:354c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.128.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.132.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.136.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.136.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.140.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.140.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.72.142.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53018 whose prefix no peer sees AS53018 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.72.128.0/20 | TC | No ROA |
| 177.72.128.0/24 | TC | Valid |
| 177.72.137.0/24 | TC | Valid |
| 177.72.140.0/24 | TC | Valid |
| 177.72.141.0/24 | TC | Valid |
| 177.72.142.0/24 | TC | Valid |
| 177.72.143.0/24 | 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.