Network · data from 2026-11-12
AS263140 AS263140 - Net-Uai Internet Provider LTDA ME
Registry name: AS263140 - Net-Uai Internet Provider LTDA ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263140, 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.205.144.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 168.205.146.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.6.140.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.6.142.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 168.205.144.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 191.6.140.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 191.6.143.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 2804:175c::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
AS263140 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 21 are in fix.csv.
- Route object: RIR8
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 168.205.144.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.146.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.140.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.142.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.144.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.140.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.6.143.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:175c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263140 whose prefix no peer sees AS263140 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.205.144.0/24 | TC | Valid |
| 168.205.145.0/24 | TC | Valid |
| 168.205.146.0/24 | TC | Valid |
| 168.205.147.0/24 | TC | Valid |
| 191.6.140.0/24 | TC | Valid |
| 191.6.141.0/24 | TC | Valid |
| 191.6.142.0/24 | TC | Valid |
| 2804:175c::/33 | TC | Valid |
| 2804:175c::/34 | TC | Valid |
| 2804:175c:4000::/34 | TC | Valid |
| 2804:175c:8000::/33 | TC | Valid |
| 2804:175c:8000::/34 | TC | Valid |
| 2804:175c:c000::/34 | 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.