Network · data from 2026-11-12
AS61830 NETTRON TELECOMUNICACOES LTDA - ME
Registry name: AS61830 - NETTRON PROVEDOR DE INTERNET LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61830, 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.
| 201.140.240.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.240.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.240.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.241.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.242.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.242.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.140.243.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:19fc::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS61830: AS61830:AS-NETTRON-ALL. 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 (AS61830 isn't in the set, or no route object for AS61830 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 | AS61830 in it | Not covered |
|---|---|---|---|---|---|
| AS61830:AS-NETTRON-ALL | TC | 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 14 are in fix.csv.
- Route object: RIR8
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 201.140.240.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.240.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.240.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.241.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.242.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.242.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.140.243.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:19fc::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61830 whose prefix no peer sees AS61830 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:19fc::/33 | RADB, TC | Valid |
| 2804:19fc::/34 | RADB, TC | Valid |
| 2804:19fc:4000::/34 | RADB, TC | Valid |
| 2804:19fc:8000::/33 | RADB, TC | Valid |
| 2804:19fc:8000::/34 | TC | Valid |
| 2804:19fc: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.