Network · data from 2026-11-12
AS141030 CIRCLENETWORK-AS-AP - CIRCLE NETWORK
Registry name: CIRCLENETWORK-AS-AP - CIRCLE NETWORK, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141030, 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.
| 2400:3dc0:7b:5::/64 | Invalid: origin | None | 2 0%low visibility |
| 165.101.13.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 2400:3dc0:4e::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:4f::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:52::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:53::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:54::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:59::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:81::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:3dc0:41::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:42::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:47::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:48::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:4d::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:50::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:51::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:55::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:56::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:5c::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:5d::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:5e::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:5f::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:62::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:63::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:64::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:65::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:67::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:6b::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:6d::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:6e::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:72::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:73::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:74::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:75::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:76::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:77::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:79::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:7a::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:82::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2400:3dc0:4b::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:7d::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:7f::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:90::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:91::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:92::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:93::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:94::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:95::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:96::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:3dc0:97::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS141030 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2400:3dc0:7b:5::/64 | ROAs covering it name AS134371, not AS141030. If AS141030 should announce it, add a ROA for AS141030. |
| Route object: none | 2400:3dc0:7b:5::/64 | No route object for it. Add a route object with origin AS141030 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141030 whose prefix no peer sees AS141030 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2400:3dc0:44::/48 | APNIC | Valid |
| 2400:3dc0:4a::/48 | APNIC | Valid |
| 2400:3dc0:66::/48 | APNIC | Valid |
| 2400:3dc0:7c::/48 | APNIC | Valid |
| 2400:3dc0:7e::/48 | APNIC | 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.