Network · data from 2026-11-12
AS263305 AS263305 - NET.COM TELECOMUNICACOES EIRELI
Registry name: AS263305 - NET.COM TELECOMUNICACOES EIRELI, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263305, 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.38.92.0/22 | Valid | None | 672 100% |
| 177.38.92.0/23 | Valid | None | 672 100% |
| 177.38.92.0/24 | Valid | None | 672 100% |
| 177.38.93.0/24 | Valid | None | 672 100% |
| 191.6.132.0/23 | Valid | Nonecovered by 191.6.132.0/22 | 672 100% |
| 191.6.134.0/23 | Valid | Nonecovered by 191.6.132.0/22 | 672 100% |
| 2804:13f8::/33 | Valid | Nonecovered by 2804:13f8::/32 | 634 100% |
| 2804:13f8:8000::/33 | Valid | Nonecovered by 2804:13f8::/32 | 634 100% |
| 191.6.132.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 191.6.132.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 191.6.133.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 191.6.134.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 191.6.135.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:13f8::/32 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS263305 isn't in PeeringDB, where networks name their AS-SET.
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 14 are in fix.csv.
- Route object: none8
- Route object: RIR6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.38.92.0/22 | No route object for it. Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 177.38.92.0/23 | No route object for it. Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 177.38.92.0/24 | No route object for it. Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 177.38.93.0/24 | No route object for it. Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 191.6.132.0/23 | No route object for it. A route object for 191.6.132.0/22 with origin AS263305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 191.6.134.0/23 | No route object for it. A route object for 191.6.132.0/22 with origin AS263305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 2804:13f8::/33 | No route object for it. A route object for 2804:13f8::/32 with origin AS263305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: none | 2804:13f8:8000::/33 | No route object for it. A route object for 2804:13f8::/32 with origin AS263305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263305 in the RIR database for the space. |
| Route object: RIR | 191.6.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.133.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.134.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.135.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:13f8::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS263305 is announced.
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.