bgpreport

Network · data from 2026-11-12

AS133150 GTISI-AS-AP - GGS Technical Information Services Inc.

Registry name: GTISI-AS-AP - GGS Technical Information Services Inc., PH · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 57.1% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
1No ROA 3 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS133150, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133150, 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.

87.84.71.0/24 Invalid: origin None 3 0%low visibility 3
150.251.231.0/24 Invalid: origin Other origin only 1 0%low visibility 1
213.109.154.0/24 No ROA Other origin only 2 0%low visibility 2
2.27.107.0/24 Valid Other IRR onlyRADB 673 100% 66
89.33.12.0/24 Valid Other IRR onlyRADB 673 100% 66
155.117.151.0/24 Valid Other IRR onlyRADB 673 100% 66
45.159.92.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS133150 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 10 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin87.84.71.0/24ROAs covering it name AS834, not AS133150. If AS133150 should announce it, add a ROA for AS133150.3 of 673
Route object: none87.84.71.0/24No route object for it. Add a route object with origin AS133150 in the RIR database for the space.3 of 673
ROA: origin150.251.231.0/24ROAs covering it name AS218879, not AS133150. If AS133150 should announce it, add a ROA for AS133150.1 of 673
Route object: none150.251.231.0/24Route objects for it name AS218879. Add a route object with origin AS133150 in the RIR database for the space.1 of 673
ROA: none213.109.154.0/24No ROA covers it. Add a ROA for AS133150, maxLength 24.2 of 673
Route object: none213.109.154.0/24Route objects for it name AS25236. Add a route object with origin AS133150 in the RIR database for the space.2 of 673
Route object: RIR2.27.107.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.33.12.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR155.117.151.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

213.220.62.0/24RADBValid

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.