Network · data from 2026-11-12
AS61946 AS61946 - DB3 SERVICOS DE TELECOMUNICACOES S.A
Registry name: AS61946 - DB3 SERVICOS DE TELECOMUNICACOES S.A, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61946, 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.
| 10.230.0.0/24 bogon | No ROA | None | 0 0%low visibility |
| 172.16.245.0/24 bogon | No ROA | None | 0 0%low visibility |
| 192.168.52.0/24 bogon | No ROA | None | 0 0%low visibility |
| 201.139.184.0/23 | Valid | Nonecovered by 201.139.184.0/21 | 220 33% |
| 201.139.188.0/23 | Valid | Nonecovered by 201.139.184.0/21 | 220 33% |
| 201.139.186.0/23 | Valid | Nonecovered by 201.139.184.0/21 | 219 33% |
| 201.139.190.0/23 | Valid | Nonecovered by 201.139.184.0/21 | 219 33% |
| 201.139.184.0/21 | Valid | Other IRR onlyRADB | 669 99% |
AS-SET
AS61946 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 9 are in fix.csv.
- Bogon prefix3
- Route object: none4
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Bogon prefix | 10.230.0.0/24 | In IANA's special-purpose registry: Private-Use (RFC 1918). |
| Bogon prefix | 172.16.245.0/24 | In IANA's special-purpose registry: Private-Use (RFC 1918). |
| Bogon prefix | 192.168.52.0/24 | In IANA's special-purpose registry: Private-Use (RFC 1918). |
| Route object: none | 201.139.184.0/23 | No route object for it. A route object for 201.139.184.0/21 with origin AS61946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61946 in the RIR database for the space. |
| Route object: none | 201.139.188.0/23 | No route object for it. A route object for 201.139.184.0/21 with origin AS61946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61946 in the RIR database for the space. |
| Route object: none | 201.139.186.0/23 | No route object for it. A route object for 201.139.184.0/21 with origin AS61946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61946 in the RIR database for the space. |
| Route object: none | 201.139.190.0/23 | No route object for it. A route object for 201.139.184.0/21 with origin AS61946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61946 in the RIR database for the space. |
| Route object: RIR | 201.139.184.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61946 whose prefix no peer sees AS61946 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:18ac::/32 | RADB | No ROA |
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.