bgpreport

Network · data from 2026-11-12

AS138501 Unified Core

Registry name: UNIFIED-AS-AP - Unified Core Limited, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138501, 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.
103.127.57.0/24 Valid RIR databaseAPNIC 673 100% 69
160.187.116.0/24 Valid RIR databaseAPNIC 672 100% 66
103.127.56.0/24 Valid RIR databaseAPNIC 669 99% 68
223.165.2.0/24 Valid RIR databaseAPNIC 669 99% 67
223.165.3.0/24 Valid RIR databaseAPNIC 669 99% 68
103.127.56.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
103.127.58.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
103.127.59.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

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

  • Route object: not announced31

Route objects not announced

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

2405:9a40::/32APNICValid
2405:9a40::/33APNICValid
2405:9a40::/34APNICValid
2405:9a40::/35APNICValid
2405:9a40::/36APNICValid
2405:9a40:1000::/36APNICValid
2405:9a40:2000::/35APNICValid
2405:9a40:2000::/36APNICValid
2405:9a40:3000::/36APNICValid
2405:9a40:4000::/34APNICValid
2405:9a40:4000::/35APNICValid
2405:9a40:4000::/36APNICValid
2405:9a40:5000::/36APNICValid
2405:9a40:6000::/35APNICValid
2405:9a40:6000::/36APNICValid
2405:9a40:7000::/36APNICValid
2405:9a40:8000::/33APNICValid
2405:9a40:8000::/34APNICValid
2405:9a40:8000::/35APNICValid
2405:9a40:8000::/36APNICValid
2405:9a40:9000::/36APNICValid
2405:9a40:a000::/35APNICValid
2405:9a40:a000::/36APNICValid
2405:9a40:b000::/36APNICValid
2405:9a40:c000::/34APNICValid
2405:9a40:c000::/35APNICValid
2405:9a40:c000::/36APNICValid
2405:9a40:d000::/36APNICValid
2405:9a40:e000::/35APNICValid
2405:9a40:e000::/36APNICValid
2405:9a40:f000::/36APNICValid

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.