Network · data from 2026-11-12
AS52600 Digitotal Networks
Registry name: AS52600 - Digitotal Networks Telecomunicacoes ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52600, 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.137.113.0/24 | Invalid: maxLength | Nonecovered by 177.137.112.0/22 | 80 12% |
| 177.137.112.0/21 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:d1c::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 177.137.112.0/22 | Valid | Other IRR onlyTC | 22 3%low visibility |
| 177.137.115.0/24 | Valid | Other IRR onlyTC | 0 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS52600: AS52600:AS-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 (AS52600 isn't in the set, or no route object for AS52600 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 | AS52600 in it | Not covered |
|---|---|---|---|---|---|
| AS52600:AS-ALL | TC | 10 | 2 | 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 10 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 177.137.113.0/24 | ROA 177.137.112.0/21 AS52600 has maxLength 21; ROA 177.137.112.0/22 AS52600 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 177.137.113.0/24. |
| Route object: none | 177.137.113.0/24 | No route object for it. A route object for 177.137.112.0/22 with origin AS52600 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52600 in the RIR database for the space. |
| Route object: RIR | 177.137.112.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:d1c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.137.112.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.137.115.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52600 whose prefix no peer sees AS52600 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.137.116.0/23 | TC | Valid |
| 177.137.117.0/24 | TC | Valid |
| 2804:d1c:90::/44 | RADB | Valid |
| 2804:d1c:d000::/44 | RADB | 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.