Network · data from 2026-11-12
AS52564 Biazi Telecom
Registry name: AS52564 - Biazi Telecom, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52564, 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.
| 131.161.36.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 131.161.37.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 131.161.39.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 138.219.144.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 138.219.145.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 138.219.146.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 138.219.147.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.157.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.159.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.91.236.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.91.237.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.91.238.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.91.239.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 187.62.72.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 187.62.73.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 187.62.74.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 187.62.75.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 131.161.38.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 177.85.156.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 177.85.158.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:1eb8::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 633 100% |
| 2804:1eb8:6e8::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:7e8::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:8e8::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:b1a0::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:b1a5::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:b1a6::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:b1a8::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:cafe::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:f000::/39 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:f0b0::/44 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:f0c0::/44 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:ffff::/48 | Valid | Other IRR onlyTC | 633 100% |
| 2804:1eb8:b1a7::/48 | Valid | Other IRR onlyTC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS52564: AS52564:AS-52564-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 (AS52564 isn't in the set, or no route object for AS52564 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 | AS52564 in it | Not covered |
|---|---|---|---|---|---|
| AS52564:AS-52564-GLOBAL | TC | 12 | 4 | 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 49 are in fix.csv.
- Route object: RIR34
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.161.36.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.37.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.39.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.144.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.145.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.146.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.147.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.157.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.159.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.236.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.237.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.238.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.239.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.72.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.73.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.74.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.62.75.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.38.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.156.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.158.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:6e8::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:7e8::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:8e8::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:b1a0::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:b1a5::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:b1a6::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:b1a8::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:cafe::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:f000::/39 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:f0b0::/44 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:f0c0::/44 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:ffff::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1eb8:b1a7::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52564 whose prefix no peer sees AS52564 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.161.36.0/22 | RADB, TC | Valid |
| 131.161.36.0/23 | TC | Valid |
| 131.161.38.0/23 | TC | Valid |
| 138.219.144.0/22 | RADB, TC | Valid |
| 138.219.144.0/23 | TC | Valid |
| 138.219.146.0/23 | TC | Valid |
| 177.85.156.0/22 | RADB, TC | Valid |
| 177.85.156.0/23 | TC | Valid |
| 177.85.158.0/23 | TC | Valid |
| 177.91.236.0/22 | TC | Valid |
| 177.91.236.0/23 | TC | Valid |
| 177.91.238.0/23 | TC | Valid |
| 187.62.72.0/22 | RADB, TC | Valid |
| 187.62.72.0/23 | TC | Valid |
| 187.62.74.0/23 | 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.