Network · data from 2026-11-12
AS61773 AS61773 - G+ NETWORK TELECOM EIRELI - ME
Registry name: AS61773 - G+ NETWORK TELECOM EIRELI - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61773, 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.
| 192.207.200.0/24 | No ROA | Nonecovered by 192.207.200.0/22 | 668 99% |
| 192.207.201.0/24 | No ROA | Nonecovered by 192.207.200.0/22 | 668 99% |
| 192.207.202.0/24 | No ROA | Nonecovered by 192.207.200.0/22 | 668 99% |
| 192.207.203.0/24 | No ROA | Nonecovered by 192.207.200.0/22 | 668 99% |
| 200.225.104.0/24 | No ROA | Nonecovered by 200.225.104.0/22 | 667 99% |
| 200.225.105.0/24 | No ROA | Nonecovered by 200.225.104.0/22 | 667 99% |
| 200.225.106.0/24 | No ROA | Nonecovered by 200.225.104.0/22 | 667 99% |
| 200.225.107.0/24 | No ROA | Nonecovered by 200.225.104.0/22 | 667 99% |
| 192.207.200.0/22 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 668 99% |
| 200.225.104.0/22 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 667 99% |
| 2804:1920::/32 | No ROA | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
AS61773 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 22 are in fix.csv.
- ROA: none11
- Route object: none8
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.207.200.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 192.207.200.0/24 | No route object for it. A route object for 192.207.200.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 192.207.201.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 192.207.201.0/24 | No route object for it. A route object for 192.207.200.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 192.207.202.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 192.207.202.0/24 | No route object for it. A route object for 192.207.200.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 192.207.203.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 192.207.203.0/24 | No route object for it. A route object for 192.207.200.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 200.225.104.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 200.225.104.0/24 | No route object for it. A route object for 200.225.104.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 200.225.105.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 200.225.105.0/24 | No route object for it. A route object for 200.225.104.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 200.225.106.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 200.225.106.0/24 | No route object for it. A route object for 200.225.104.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 200.225.107.0/24 | No ROA covers it. Add a ROA for AS61773, maxLength 24. |
| Route object: none | 200.225.107.0/24 | No route object for it. A route object for 200.225.104.0/22 with origin AS61773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61773 in the RIR database for the space. |
| ROA: none | 192.207.200.0/22 | No ROA covers it. Add a ROA for AS61773, maxLength 22. |
| Route object: RIR | 192.207.200.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 200.225.104.0/22 | No ROA covers it. Add a ROA for AS61773, maxLength 22. |
| Route object: RIR | 200.225.104.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1920::/32 | No ROA covers it. Add a ROA for AS61773, maxLength 32. |
| Route object: RIR | 2804:1920::/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 AS61773 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.