bgpreport

Network · data from 2026-11-12

AS132204 CORETELNET-AS-AP - CORETEL NETWORKS (INTERNATIONAL) PTE LTD

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

2IPv4 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
9Route objects not announced registered with origin AS132204, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132204, 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.
206.131.200.0/24 Valid RIR databaseAPNIC, RADB 641 95% 67
206.131.201.0/24 Valid RIR databaseAPNIC, RADB 641 95% 67

AS-SET

AS132204 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 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

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

45.254.232.0/22RADBNo ROA
64.66.32.0/24RADBNo ROA
103.6.248.0/22RADBNo ROA
103.23.96.0/22RADBNo ROA
103.64.136.0/22RADBNo ROA
203.208.22.0/24APNIC, RADBValid
206.131.192.0/20RADBNo ROA
206.131.192.0/24APNIC, RADBValid
206.131.199.0/24APNIC, RADBValid

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.