bgpreport

Network · data from 2026-11-12

AS133717 KORE DIGITAL

Registry name: KOREDIGITAL-AS - KORE DIGITAL, IN · PeeringDB

1IPv4 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
0Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS133717, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS133717, 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.
111.125.247.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

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

  • Route object: not announced23

Route objects not announced

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

103.41.236.0/22APNIC, RADBValid
103.41.236.0/23APNICValid
103.41.236.0/24APNICValid
103.41.237.0/24APNICValid
103.41.238.0/23APNICValid
103.41.238.0/24APNICValid
103.41.239.0/24APNICValid
111.125.214.0/23APNICValid
111.125.214.0/24APNIC, RADBValid
111.125.215.0/24APNICValid
111.125.232.0/24RADBNo ROA
111.125.234.0/23RADBNo ROA
111.125.235.0/24APNICNo ROA
111.125.237.0/24APNIC, RADBNo ROA
111.125.238.0/23APNIC, RADBValid
111.125.238.0/24APNICValid
111.125.239.0/24APNICValid
111.125.240.0/24APNIC, RADBNo ROA
111.125.243.0/24APNIC, RADBNo ROA
111.125.245.0/24APNIC, RADBNo ROA
111.125.246.0/23APNIC, RADBValid
111.125.246.0/24APNICValid
111.125.248.0/24APNIC, RADBNo ROA

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.