bgpreport

Network · data from 2026-11-12

AS56274 GM-AP-SGDC - GM Asia Pacific, Singapore

Registry name: GM-AP-SGDC - GM Asia Pacific, Singapore, SG · not in PeeringDB

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

Announced routes

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

2400:bb00:101::/48 No ROA None 635 100% 67
2400:bb00:102::/48 No ROA None 635 100% 67
198.208.31.0/24 Valid RIR databaseARIN 673 100% 67
198.208.38.0/24 Valid RIR databaseARIN 673 100% 67
198.208.96.0/21 Valid RIR databaseARIN 673 100% 67
198.208.96.0/22 Valid RIR databaseARIN 673 100% 67
198.208.100.0/22 Valid RIR databaseARIN 673 100% 67
198.208.133.0/24 Valid RIR databaseARIN 673 100% 67
198.208.134.0/24 Valid RIR databaseARIN 673 100% 67
198.208.216.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS56274 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 6 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2400:bb00:101::/48No ROA covers it. Add a ROA for AS56274, maxLength 48.635 of 636
Route object: none2400:bb00:101::/48No route object for it. Add a route object with origin AS56274 in the RIR database for the space.635 of 636
ROA: none2400:bb00:102::/48No ROA covers it. Add a ROA for AS56274, maxLength 48.635 of 636
Route object: none2400:bb00:102::/48No route object for it. Add a route object with origin AS56274 in the RIR database for the space.635 of 636

Route objects not announced

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

198.208.9.0/24ARINValid
198.208.208.0/24ARINValid

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.