bgpreport

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

10IPv4 routes 0.0% RPKI valid · 20.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS61773, seen from no peer

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% 67
192.207.201.0/24 No ROA Nonecovered by 192.207.200.0/22 668 99% 67
192.207.202.0/24 No ROA Nonecovered by 192.207.200.0/22 668 99% 67
192.207.203.0/24 No ROA Nonecovered by 192.207.200.0/22 668 99% 67
200.225.104.0/24 No ROA Nonecovered by 200.225.104.0/22 667 99% 67
200.225.105.0/24 No ROA Nonecovered by 200.225.104.0/22 667 99% 67
200.225.106.0/24 No ROA Nonecovered by 200.225.104.0/22 667 99% 67
200.225.107.0/24 No ROA Nonecovered by 200.225.104.0/22 667 99% 67
192.207.200.0/22 No ROA Other IRR onlyALTDB, NTTCOM, RADB 668 99% 67
200.225.104.0/22 No ROA Other IRR onlyALTDB, NTTCOM, RADB 667 99% 67
2804:1920::/32 No ROA Other IRR onlyALTDB, RADB 634 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: none192.207.200.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.668 of 673
Route object: none192.207.200.0/24No 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.668 of 673
ROA: none192.207.201.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.668 of 673
Route object: none192.207.201.0/24No 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.668 of 673
ROA: none192.207.202.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.668 of 673
Route object: none192.207.202.0/24No 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.668 of 673
ROA: none192.207.203.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.668 of 673
Route object: none192.207.203.0/24No 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.668 of 673
ROA: none200.225.104.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.667 of 673
Route object: none200.225.104.0/24No 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.667 of 673
ROA: none200.225.105.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.667 of 673
Route object: none200.225.105.0/24No 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.667 of 673
ROA: none200.225.106.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.667 of 673
Route object: none200.225.106.0/24No 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.667 of 673
ROA: none200.225.107.0/24No ROA covers it. Add a ROA for AS61773, maxLength 24.667 of 673
Route object: none200.225.107.0/24No 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.667 of 673
ROA: none192.207.200.0/22No ROA covers it. Add a ROA for AS61773, maxLength 22.668 of 673
Route object: RIR192.207.200.0/22Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.225.104.0/22No ROA covers it. Add a ROA for AS61773, maxLength 22.667 of 673
Route object: RIR200.225.104.0/22Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:1920::/32No ROA covers it. Add a ROA for AS61773, maxLength 32.634 of 636
Route object: RIR2804:1920::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636

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.