Network · data from 2026-11-12
AS52758 Global Network Telecomunicações do Brasil
Registry name: AS52758 - Global Network Telecomunicacoes do Brasil Ltda., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52758, 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.
| 2804:b38::/33 | Valid | Nonecovered by 2804:b38::/32 | 634 100% |
| 2804:b38:8000::/33 | Valid | Nonecovered by 2804:b38::/32 | 634 100% |
| 177.38.184.0/21 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 201.131.240.0/21 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:b38::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 177.38.185.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 177.38.186.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 177.38.188.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 177.38.190.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 177.38.191.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 201.131.240.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 201.131.242.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 201.131.243.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 201.131.244.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 201.131.245.0/24 | Valid | Other IRR onlyTC | 210 31% |
| 177.38.184.0/24 | Valid | Other IRR onlyTC | 209 31% |
| 177.38.187.0/24 | Valid | Other IRR onlyTC | 209 31% |
| 201.131.246.0/24 | Valid | Other IRR onlyTC | 209 31% |
| 201.131.247.0/24 | Valid | Other IRR onlyTC | 209 31% |
| 177.38.184.0/22 | Valid | Other IRR onlyTC | 207 31% |
| 177.38.184.0/23 | Valid | Other IRR onlyTC | 207 31% |
| 177.38.188.0/22 | Valid | Other IRR onlyTC | 207 31% |
| 177.38.188.0/23 | Valid | Other IRR onlyTC | 207 31% |
| 177.38.190.0/23 | Valid | Other IRR onlyTC | 207 31% |
| 201.131.240.0/22 | Valid | Other IRR onlyTC | 207 31% |
| 201.131.240.0/23 | Valid | Other IRR onlyRADB, TC | 207 31% |
| 201.131.242.0/23 | Valid | Other IRR onlyTC | 207 31% |
| 201.131.244.0/22 | Valid | Other IRR onlyTC | 207 31% |
| 201.131.244.0/23 | Valid | Other IRR onlyTC | 207 31% |
| 201.131.246.0/23 | Valid | Other IRR onlyTC | 207 31% |
AS-SET
PeeringDB's irr_as_set for AS52758: AS52758:AS-GLOBAL-LINES. 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 (AS52758 isn't in the set, or no route object for AS52758 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 | AS52758 in it | Not covered |
|---|---|---|---|---|---|
| AS52758:AS-GLOBAL-LINES | TC | 4 | 3 | 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 33 are in fix.csv.
- Route object: none2
- Route object: RIR28
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:b38::/33 | No route object for it. A route object for 2804:b38::/32 with origin AS52758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52758 in the RIR database for the space. |
| Route object: none | 2804:b38:8000::/33 | No route object for it. A route object for 2804:b38::/32 with origin AS52758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52758 in the RIR database for the space. |
| Route object: RIR | 177.38.184.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.240.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:b38::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.185.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.186.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.188.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.190.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.191.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.240.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.242.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.243.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.244.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.245.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.184.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.187.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.246.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.247.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.184.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.184.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.188.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.188.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.190.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.240.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.240.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.242.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.244.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.244.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.246.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52758 whose prefix no peer sees AS52758 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.38.186.0/23 | TC | Valid |
| 177.38.189.0/24 | TC | Valid |
| 201.131.241.0/24 | 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.