bgpreport

Network · data from 2026-11-12

AS134677 Dromatics Systems Pte Ltd

Registry name: IDC-AS-AP - Dromatics Systems Pte Ltd, SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134677, 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.
92.113.124.0/24 Valid Other origin onlycovered by 92.113.124.0/23 668 99% 67
61.15.193.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
146.19.216.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.245.90.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
181.41.217.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
202.73.4.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.155.141.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
31.58.152.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
45.127.32.0/24 Valid RIR databaseAPNIC 672 100% 68
45.127.33.0/24 Valid RIR databaseAPNIC 672 100% 68
45.127.34.0/24 Valid RIR databaseAPNIC 672 100% 68
45.127.35.0/24 Valid RIR databaseAPNIC 672 100% 68
77.216.8.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
104.234.174.0/24 Valid RIR databaseARIN, RADB 672 100% 68
104.234.177.0/24 Valid RIR databaseARIN, RADB 672 100% 68
104.234.26.0/24 Valid RIR databaseARIN, RADB 671 100% 67
166.88.227.0/24 Valid RIR databaseARIN, RADB 671 100% 67
103.195.188.0/22 Valid RIR databaseAPNIC 669 99% 68
103.195.188.0/24 Valid RIR databaseAPNIC 669 99% 68
103.195.190.0/24 Valid RIR databaseAPNIC 669 99% 68
103.195.191.0/24 Valid RIR databaseAPNIC 669 99% 68
178.239.117.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
103.195.189.0/24 Valid RIR databaseAPNIC 666 99% 68
166.0.22.0/24 Valid RIR databaseARIN, RADB 651 97% 67
77.216.5.0/24 Valid RIR databaseRADB, RIPE 650 97% 67
77.216.6.0/24 Valid RIR databaseRADB, RIPE 650 97% 67
2a0f:9400:7393::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:9400:7394::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:9400:7390::/48 Valid RIR databaseRIPE 635 100% 67
2a0f:9400:7395::/48 Valid RIR databaseRIPE 635 100% 67
2001:df4:c140::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS134677'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 7 are in fix.csv.

  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none92.113.124.0/24Route objects for it name AS36530. A route object for 92.113.124.0/23 with origin AS134677 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134677 in the RIR database for the space.668 of 673

Route objects not announced

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

45.127.32.0/22APNICValid
92.113.124.0/23RADB, RIPEValid
2001:470:e3::/48ARINValid
2a0f:9400:7391::/48RIPEValid
2a0f:9400:7392::/48RIPEValid
2a13:9500:75::/48RIPEValid

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.