bgpreport

Network · data from 2026-11-12

AS27789 GreenDot Ltd.

Registry name: AS27789 - GREENDOT, TT · PeeringDB

33IPv4 routes 84.8% RPKI valid · 21.2% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
5No ROA 27 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS27789, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27789, 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.
2800:70:9400::/38 Invalid: maxLength Nonecovered by 2800:70::/32 19 3%low visibility 10
201.221.68.0/24 No ROA Nonecovered by 201.221.64.0/19 673 100% 67
201.221.95.0/24 No ROA Nonecovered by 201.221.64.0/19 673 100% 67
190.93.64.0/18 No ROA None 672 100% 67
201.221.86.0/24 No ROA Nonecovered by 201.221.64.0/19 2 0%low visibility 2
201.221.64.0/19 No ROA Other IRR onlyALTDB 673 100% 67
201.221.66.0/24 Valid Nonecovered by 201.221.64.0/22 673 100% 67
201.221.67.0/24 Valid Nonecovered by 201.221.64.0/22 673 100% 67
201.221.72.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.73.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.75.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.76.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.78.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.79.0/24 Valid Nonecovered by 201.221.72.0/21 673 100% 67
201.221.81.0/24 Valid Nonecovered by 201.221.80.0/22 673 100% 67
201.221.82.0/24 Valid Nonecovered by 201.221.80.0/22 673 100% 67
190.93.2.0/23 Valid Nonecovered by 190.93.0.0/22 672 100% 67
190.93.12.0/24 Valid Nonecovered by 190.93.8.0/21 672 100% 67
190.93.15.0/24 Valid Nonecovered by 190.93.8.0/21 672 100% 67
190.93.16.0/24 Valid Nonecovered by 190.93.0.0/19 672 100% 67
190.93.18.0/24 Valid Nonecovered by 190.93.0.0/19 672 100% 67
190.93.25.0/24 Valid Nonecovered by 190.93.24.0/22 672 100% 67
190.93.26.0/24 Valid Nonecovered by 190.93.24.0/22 672 100% 67
190.93.27.0/24 Valid Nonecovered by 190.93.24.0/22 672 100% 67
190.93.28.0/24 Valid Nonecovered by 190.93.28.0/23 672 100% 67
200.12.241.0/24 Valid Nonecovered by 200.12.240.0/21 672 100% 67
200.12.244.0/22 Valid Nonecovered by 200.12.240.0/21 672 100% 67
190.93.13.0/24 Valid Nonecovered by 190.93.8.0/21 669 99% 67
190.93.0.0/20 Valid Other IRR onlyRADB 672 100% 67
190.93.17.0/24 Valid Other IRR onlyRADB 672 100% 67
190.93.30.0/24 Valid Other IRR onlyRADB 672 100% 67
23.3.72.0/24 Valid RIR databaseARIN 673 100% 67
190.93.0.0/19 Valid RIR databaseLACNIC, RADB 672 100% 67
200.12.240.0/21 Valid RIR databaseLACNIC 672 100% 67
2800:70::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

AS27789's PeeringDB record names no 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 58 are in fix.csv.

  • ROA: maxLength1
  • ROA: none5
  • Route object: none27
  • Route object: RIR4
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: maxLength2800:70:9400::/38ROA 2800:70::/32 AS27789 has maxLength 36; the route is a /38. Raise the maxLength, or add a ROA for 2800:70:9400::/38.19 of 636
Route object: none2800:70:9400::/38No route object for it. A route object for 2800:70::/32 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.19 of 636
ROA: none201.221.68.0/24No ROA covers it. Add a ROA for AS27789, maxLength 24.673 of 673
Route object: none201.221.68.0/24No route object for it. A route object for 201.221.64.0/19 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
ROA: none201.221.95.0/24No ROA covers it. Add a ROA for AS27789, maxLength 24.673 of 673
Route object: none201.221.95.0/24No route object for it. A route object for 201.221.64.0/19 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
ROA: none190.93.64.0/18No ROA covers it. Add a ROA for AS27789, maxLength 18.672 of 673
Route object: none190.93.64.0/18No route object for it. Add a route object with origin AS27789 in the RIR database for the space.672 of 673
ROA: none201.221.86.0/24No ROA covers it. Add a ROA for AS27789, maxLength 24.2 of 673
Route object: none201.221.86.0/24No route object for it. A route object for 201.221.64.0/19 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.2 of 673
ROA: none201.221.64.0/19No ROA covers it. Add a ROA for AS27789, maxLength 19.673 of 673
Route object: RIR201.221.64.0/19Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: none201.221.66.0/24No route object for it. A route object for 201.221.64.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.67.0/24No route object for it. A route object for 201.221.64.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.72.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.73.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.75.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.76.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.78.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.79.0/24No route object for it. A route object for 201.221.72.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.81.0/24No route object for it. A route object for 201.221.80.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none201.221.82.0/24No route object for it. A route object for 201.221.80.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.673 of 673
Route object: none190.93.2.0/23No route object for it. A route object for 190.93.0.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.12.0/24No route object for it. A route object for 190.93.8.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.15.0/24No route object for it. A route object for 190.93.8.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.16.0/24No route object for it. A route object for 190.93.0.0/19 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.18.0/24No route object for it. A route object for 190.93.0.0/19 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.25.0/24No route object for it. A route object for 190.93.24.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.26.0/24No route object for it. A route object for 190.93.24.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.27.0/24No route object for it. A route object for 190.93.24.0/22 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.28.0/24No route object for it. A route object for 190.93.28.0/23 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none200.12.241.0/24No route object for it. A route object for 200.12.240.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none200.12.244.0/22No route object for it. A route object for 200.12.240.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.672 of 673
Route object: none190.93.13.0/24No route object for it. A route object for 190.93.8.0/21 with origin AS27789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27789 in the RIR database for the space.669 of 673
Route object: RIR190.93.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.93.30.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS27789 whose prefix no peer sees AS27789 announce. Many are kept on purpose (backup routes, space announced only in some places).

190.93.0.0/22RADBValid
190.93.5.0/24RADBValid
190.93.8.0/21RADBValid
190.93.11.0/24RADBValid
190.93.24.0/22RADBValid
190.93.28.0/23RADBValid
190.93.64.0/19LACNICValid
190.93.64.0/22RADBValid
190.93.68.0/24LACNIC, RADBValid
190.93.72.0/21RADBValid
190.93.81.0/24RADBValid
190.93.95.0/24LACNIC, RADBValid
190.93.96.0/19LACNICValid
190.93.119.0/24LACNIC, RADBValid
201.221.64.0/22LACNICValid
201.221.69.0/24LACNICValid
201.221.72.0/21LACNICValid
201.221.80.0/22LACNICValid
201.221.84.0/23LACNICValid
201.221.93.0/24LACNICValid
201.221.94.0/24LACNICValid

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.