bgpreport

Network · data from 2026-11-12

AS48274 AUK-SG SOUTHEAST ASIA TELECOM(SG) PTE. LTD.

Registry name: AUK-SG SOUTHEAST ASIA TELECOM(SG) PTE. LTD., SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48274, 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.
128.14.0.0/24 Valid RIR databaseARIN 670 100% 67
2401:b480::/32 Valid RIR databaseAPNIC 635 100% 67
2a05:9340::/29 Valid RIR databaseRIPE 635 100% 67
2a11:cc0::/29 Valid RIR databaseRIPE 633 100% 67
2a11:9500::/29 Valid RIR databaseRIPE 633 100% 67
2a11:b7c0::/29 Valid RIR databaseRIPE 633 100% 67
2a11:3ac0::/29 Valid RIR databaseRIPE 632 99% 67
2a12:9f00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:4840::/29 Valid RIR databaseRIPE 630 99% 67
2a11:74c0::/29 Valid RIR databaseRIPE 630 99% 67

AS-SET

AS48274 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 5 are in fix.csv.

  • Route object: not announced5

Route objects not announced

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

66.92.10.0/24ARINValid
2a0f:3440::/29RIPEValid
2a0f:34c0::/29RIPEValid
2a11:5340::/29RIPEValid
2a12:a680::/29RIPEValid

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.