CV CEM
AS153923 · CV CEM
CV Cyber Earth Multicorp
Tools: Where can I peer with CV CEM? · Where should CV CEM peer next? · Compare CV CEM with another network
This network elsewhere: the registry history of AS153921-AS153925, the block AS153923 is in, on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
One thing to fix in CV CEM's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 18:41 UTC.
Make the changes on CV CEM's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If CV CEM has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2404:c8:0:a:0:20:3923:1 Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where CV CEM's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
These exchanges have a switch in a facility where CV CEM lists itself in PeeringDB, but don't have CV CEM as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| IIX-JakartaJakarta, Indonesia | 979 | |
| NetIXSofia, Bulgaria | 204 | |
| CXC JakartaJakarta, Indonesia | 201 | |
| BIX JakartaJakarta, Indonesia | 180 | |
| DE-CIX JakartaJakarta, Indonesia | 177 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| ILIXSurabaya, Indonesia | 122 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| CENTRO-IXPekanbaru - Jakarta, Indonesia | 39 | |
| CNI-IXJakarta, Indonesia | 18 | |
| Metta-IXJakarta, Indonesia | 16 | |
| GPMIXLampung Timur, Indonesia | 13 | |
| JDXJakarta, Indonesia | 13 | |
| BatamIX JakartaJakarta, Indonesia | 7 | |
| Super Internet eXchange (SIX)Bogor, Indonesia | 4 | |
| ABS-IXJAKARTA, Indonesia | 3 |
Facilities (2)
The buildings CV CEM lists in PeeringDB, and how many of the exchanges in each it's on.
| Datacenter APJII-CyberJakarta Selatan | 1 of 17 | |
| MettaDC POP01South Jakarta | 0 of 1 |