Network · data from 2026-11-12
AS53094 Guanhaes Internet
Registry name: AS53094 - GHNET TELECOM LTDA, BR · PeeringDB
35IPv4 routes
100.0% RPKI valid · 5.7% with a route object
5IPv6 routes
100.0% RPKI valid · 20.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
37 with no route object for this origin
16Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS53094, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS53094, 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.
| 187.102.29.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 671 100% |
| 187.102.16.0/21 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 187.102.16.0/22 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 187.102.20.0/22 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 187.102.24.0/21 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 187.102.24.0/22 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 187.102.28.0/22 | Valid | Nonecovered by 187.102.16.0/20 | 667 99% |
| 2804:2a80:20::/45 | Valid | Nonecovered by 2804:2a80::/32 | 633 100% |
| 2804:2a80:28::/45 | Valid | Nonecovered by 2804:2a80::/32 | 633 100% |
| 2804:2a80:38::/45 | Valid | Nonecovered by 2804:2a80::/32 | 633 100% |
| 2804:2a80:c000::/41 | Valid | Nonecovered by 2804:2a80::/32 | 633 100% |
| 143.208.70.0/23 | Valid | Nonecovered by 143.208.68.0/22 | 122 18% |
| 143.208.68.0/23 | Valid | Nonecovered by 143.208.68.0/22 | 121 18% |
| 187.102.16.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.18.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.20.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.22.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.24.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.26.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.30.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 121 18% |
| 187.102.28.0/23 | Valid | Nonecovered by 187.102.16.0/20 | 120 18% |
| 143.208.68.0/24 | Valid | Nonecovered by 143.208.68.0/22 | 1 0%low visibility |
| 143.208.69.0/24 | Valid | Nonecovered by 143.208.68.0/22 | 1 0%low visibility |
| 143.208.71.0/24 | Valid | Nonecovered by 143.208.68.0/22 | 1 0%low visibility |
| 187.102.16.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.17.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.18.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.20.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.21.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.22.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.23.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.24.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.25.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.26.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.28.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.30.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 187.102.31.0/24 | Valid | Nonecovered by 187.102.16.0/20 | 1 0%low visibility |
| 143.208.68.0/22 | Valid | Other IRR onlyALTDB, RADB | 667 99% |
| 187.102.16.0/20 | Valid | Other IRR onlyALTDB, RADB | 667 99% |
| 2804:2a80::/32 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS53094: AS-53094. 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 (AS53094 isn't in the set, or no route object for AS53094 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 | AS53094 in it | Not covered |
|---|---|---|---|---|---|
| AS-53094 | ALTDB | 11 | 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 40 are in fix.csv.
- Route object: none37
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 187.102.29.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.16.0/21 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.16.0/22 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.20.0/22 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.24.0/21 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.24.0/22 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.28.0/22 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 2804:2a80:20::/45 | No route object for it. A route object for 2804:2a80::/32 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 2804:2a80:28::/45 | No route object for it. A route object for 2804:2a80::/32 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 2804:2a80:38::/45 | No route object for it. A route object for 2804:2a80::/32 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 2804:2a80:c000::/41 | No route object for it. A route object for 2804:2a80::/32 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 143.208.70.0/23 | No route object for it. A route object for 143.208.68.0/22 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 143.208.68.0/23 | No route object for it. A route object for 143.208.68.0/22 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.16.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.18.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.20.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.22.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.24.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.26.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.30.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.28.0/23 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 143.208.68.0/24 | No route object for it. A route object for 143.208.68.0/22 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 143.208.69.0/24 | No route object for it. A route object for 143.208.68.0/22 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 143.208.71.0/24 | No route object for it. A route object for 143.208.68.0/22 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.16.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.17.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.18.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.20.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.21.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.22.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.23.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.24.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.25.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.26.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.28.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.30.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: none | 187.102.31.0/24 | No route object for it. A route object for 187.102.16.0/20 with origin AS53094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53094 in the RIR database for the space. |
| Route object: RIR | 143.208.68.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.102.16.0/20 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2a80::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS53094 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.