Network · data from 2026-11-12
AS134041 Ncore Creative Technologies
Registry name: NCORECREATIVETECHNOLOGIES-AS-IN - Ncore Creative Technologies Pvt.Ltd., IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134041, 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.
| 2402:ccc0::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS134041: AS134041:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS134041 isn't in the set, or no route object for AS134041 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS134041 in it | Not covered |
|---|---|---|---|---|---|
| AS134041:AS-CUSTOMERS | APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 714 | 73 | Yes | 0 |
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 14 are in fix.csv.
- AS-SET: missing member5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS134041:AS-CUSTOMERS | AS134041:AS-CUSTOMERS (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS134041:AS-CUSTOMERS | AS134041:AS-CUSTOMERS (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS134041:AS-CUSTOMERS | AS134041:AS-CUSTOMERS (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS134041:AS-CUSTOMERS | AS134041:AS-CUSTOMERS (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS134041:AS-CUSTOMERS | AS134041:AS-CUSTOMERS (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS134041 whose prefix no peer sees AS134041 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.6.90.0/23 | APNIC | Valid |
| 103.6.90.0/24 | APNIC | Valid |
| 103.6.91.0/24 | APNIC | Valid |
| 103.61.195.0/24 | APNIC | Valid |
| 103.162.178.0/24 | APNIC | Valid |
| 103.178.193.0/24 | APNIC | Valid |
| 103.193.255.0/24 | APNIC | Valid |
| 103.216.200.0/24 | APNIC | Valid |
| 207.152.12.0/22 | ARIN | Valid |
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.