bgpreport

Network · data from 2026-11-12

AS133748 Coretel Networks

Registry name: CORETELNET-AS-AP - CORETEL NETWORKS (INTERNATIONAL) PTE LTD, SG · PeeringDB

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

Announced routes

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

2401:b080:141::/48 Invalid: maxLength Nonecovered by 2401:b080::/32 4 1%low visibility 4
2401:b080:651::/48 Invalid: maxLength Nonecovered by 2401:b080::/32 4 1%low visibility 4
2401:b080:652::/48 Invalid: maxLength Nonecovered by 2401:b080::/32 4 1%low visibility 4
2401:b080:653::/48 Invalid: maxLength Nonecovered by 2401:b080::/32 4 1%low visibility 4
43.249.248.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
43.249.249.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
43.249.250.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
43.249.251.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.41.128.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.41.130.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.41.131.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.192.0/24 Valid RIR databaseAPNIC 673 100% 67
206.131.193.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
206.131.195.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
206.131.198.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.199.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.202.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.203.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.206.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
206.131.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
156.225.48.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
206.131.194.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
206.131.197.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
206.131.196.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
2401:b080::/32 Valid RIR databaseAPNIC, RADB 636 100% 68
206.131.200.0/24 Valid RIR databaseAPNIC 32 5%low visibility 21
206.131.201.0/24 Valid RIR databaseAPNIC, RADB 32 5%low visibility 21

AS-SET

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

  • ROA: maxLength4
  • Route object: none4
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: maxLength2401:b080:141::/48ROA 2401:b080::/32 AS133748 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:b080:141::/48.4 of 636
Route object: none2401:b080:141::/48No route object for it. A route object for 2401:b080::/32 with origin AS133748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133748 in the RIR database for the space.4 of 636
ROA: maxLength2401:b080:651::/48ROA 2401:b080::/32 AS133748 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:b080:651::/48.4 of 636
Route object: none2401:b080:651::/48No route object for it. A route object for 2401:b080::/32 with origin AS133748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133748 in the RIR database for the space.4 of 636
ROA: maxLength2401:b080:652::/48ROA 2401:b080::/32 AS133748 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:b080:652::/48.4 of 636
Route object: none2401:b080:652::/48No route object for it. A route object for 2401:b080::/32 with origin AS133748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133748 in the RIR database for the space.4 of 636
ROA: maxLength2401:b080:653::/48ROA 2401:b080::/32 AS133748 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:b080:653::/48.4 of 636
Route object: none2401:b080:653::/48No route object for it. A route object for 2401:b080::/32 with origin AS133748 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133748 in the RIR database for the space.4 of 636

Route objects not announced

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

43.249.248.0/22APNIC, RADBValid
43.249.248.0/23APNICValid
43.249.250.0/23APNICValid
103.41.128.0/22APNIC, RADBValid
103.41.128.0/23APNICValid
103.41.129.0/24APNIC, RADBValid
103.41.130.0/23APNICValid
203.208.22.0/24APNIC, RADBValid
206.131.192.0/20APNIC, RADBNo ROA
2401:b080:1::/48APNIC, RADBValid
2401:b080:63::/48APNICValid

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.