Network · data from 2026-11-12
AS265122 AS265122 - GNET SERVICOS DE COMUNICACAO E MULTIMIDIA LTDA
Registry name: AS265122 - GNET SERVICOS DE COMUNICACAO E MULTIMIDIA LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265122, 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:2ad8:8100::/40 | Valid | Nonecovered by 2804:2ad8:8000::/33 | 631 99% |
| 143.208.92.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:2ad8::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
AS-SET
AS265122 isn't in PeeringDB, where networks name their AS-SET.
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 11 are in fix.csv.
- Route object: none1
- Route object: RIR2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:2ad8:8100::/40 | No route object for it. A route object for 2804:2ad8:8000::/33 with origin AS265122 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265122 in the RIR database for the space. |
| Route object: RIR | 143.208.92.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2ad8::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265122 whose prefix no peer sees AS265122 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.208.92.0/23 | RADB, TC | Valid |
| 143.208.92.0/24 | TC | Valid |
| 143.208.93.0/24 | TC | Valid |
| 143.208.94.0/23 | RADB, TC | Valid |
| 143.208.94.0/24 | TC | Valid |
| 143.208.95.0/24 | TC | Valid |
| 2804:2ad8::/33 | TC | Valid |
| 2804:2ad8:8000::/33 | 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.