Network · data from 2026-11-12
AS61764 Rio Grande Tecnologia e Comunic Multimidia
Registry name: AS61764 - Rio Grande Tecnologia e Comunic Multimidia Ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61764, 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.
| 201.159.84.0/22 | No ROA | Other IRR onlyRADB, TC | 671 100% |
| 2804:18f0::/32 | No ROA | Other IRR onlyRADB, TC | 635 100% |
| 2804:18f0::/33 | No ROA | Other IRR onlyRADB | 635 100% |
| 2804:18f0:8000::/33 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS61764: AS-RGOL. 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 (AS61764 isn't in the set, or no route object for AS61764 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 | AS61764 in it | Not covered |
|---|---|---|---|---|---|
| AS-RGOL | TC | 1 | 1 | 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 14 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 201.159.84.0/22 | No ROA covers it. Add a ROA for AS61764, maxLength 22. |
| Route object: RIR | 201.159.84.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:18f0::/32 | No ROA covers it. Add a ROA for AS61764, maxLength 32. |
| Route object: RIR | 2804:18f0::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:18f0::/33 | No ROA covers it. Add a ROA for AS61764, maxLength 33. |
| Route object: RIR | 2804:18f0::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:18f0:8000::/33 | No ROA covers it. Add a ROA for AS61764, maxLength 33. |
| Route object: RIR | 2804:18f0:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61764 whose prefix no peer sees AS61764 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 201.159.84.0/23 | RADB, TC | No ROA |
| 201.159.84.0/24 | TC | No ROA |
| 201.159.85.0/24 | TC | No ROA |
| 201.159.86.0/23 | RADB, TC | No ROA |
| 201.159.86.0/24 | TC | No ROA |
| 201.159.87.0/24 | RADB, TC | 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.