Network · data from 2026-11-12
AS52680 BLZNET SERVICOS DE INTERNET
Registry name: AS52680 - BLZNET SERVICOS DE INTERNET LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52680, 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.67.232.0/23 | No ROA | Nonecovered by 177.67.232.0/21 | 668 99% |
| 177.67.234.0/23 | No ROA | Nonecovered by 177.67.232.0/21 | 668 99% |
| 177.67.236.0/23 | No ROA | Nonecovered by 177.67.232.0/21 | 667 99% |
| 143.0.116.40/32 | No ROA | Nonecovered by 143.0.116.0/22 | 1 0%low visibility |
| 143.0.116.0/22 | No ROA | Other IRR onlyRADB, TC | 668 99% |
| 177.67.232.0/21 | No ROA | Other IRR onlyRADB, TC | 668 99% |
| 177.67.238.0/23 | No ROA | Other IRR onlyRADB | 667 99% |
| 2804:c20::/32 | No ROA | Other IRR onlyRADB, TC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS52680: TC::AS52680:AS-GLOBAL. 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 (AS52680 isn't in the set, or no route object for AS52680 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 | AS52680 in it | Not covered |
|---|---|---|---|---|---|
| TC::AS52680:AS-GLOBAL | TC | 22 | 2 | Yes | 1 |
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 16 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.67.232.0/23 | No ROA covers it. Add a ROA for AS52680, maxLength 23. |
| Route object: none | 177.67.232.0/23 | No route object for it. A route object for 177.67.232.0/21 with origin AS52680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52680 in the RIR database for the space. |
| ROA: none | 177.67.234.0/23 | No ROA covers it. Add a ROA for AS52680, maxLength 23. |
| Route object: none | 177.67.234.0/23 | No route object for it. A route object for 177.67.232.0/21 with origin AS52680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52680 in the RIR database for the space. |
| ROA: none | 177.67.236.0/23 | No ROA covers it. Add a ROA for AS52680, maxLength 23. |
| Route object: none | 177.67.236.0/23 | No route object for it. A route object for 177.67.232.0/21 with origin AS52680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52680 in the RIR database for the space. |
| ROA: none | 143.0.116.40/32 | No ROA covers it. Add a ROA for AS52680, maxLength 32. |
| Route object: none | 143.0.116.40/32 | No route object for it. A route object for 143.0.116.0/22 with origin AS52680 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS52680 in the RIR database for the space. |
| ROA: none | 143.0.116.0/22 | No ROA covers it. Add a ROA for AS52680, maxLength 22. |
| Route object: RIR | 143.0.116.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.67.232.0/21 | No ROA covers it. Add a ROA for AS52680, maxLength 21. |
| Route object: RIR | 177.67.232.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.67.238.0/23 | No ROA covers it. Add a ROA for AS52680, maxLength 23. |
| Route object: RIR | 177.67.238.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:c20::/32 | No ROA covers it. Add a ROA for AS52680, maxLength 32. |
| Route object: RIR | 2804:c20::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52680 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.