38.69.152.0
- No reverse DNS
- Not on blocklists
- Network
- COGENT-A
- Held by
- Cogent Communications, LLC
- Range
- 38.0.0.0 - 38.255.255.255
- CIDR
- 38.0.0.0/8
- Type
- DIRECT ALLOCATION
- Registered on
- Last updated
- Status
- active
- Report abuse to
- abuse@cogentco.com
Cogent Communications, LLC COGC
2450 N Street NW
Washington
DC
20037
United States
Cogent Communications ZC108-ARIN
2450 N Street NW
Washington
DC
20037
United States
noc@cogentco.com
+1-877-875-4311
Cogent Abuse COGEN-ARIN
2450 N street, NW
Washington
DC
20037
United States
abuse@cogentco.com
+1-877-875-4311
IP Allocation IPALL-ARIN
2450 N Street NW
Washington
DC
20037
United States
ipalloc@cogentco.com
+1-877-875-4311
And 92 more
And 67 more
From RIPEstat
103 IPv4 prefixes covering 35,328 addresses, and 5 IPv6 prefixes
And 53 more
From bgp.tools
| Exchange | Speed | Route servers |
|---|---|---|
| AMS-IX | 10 Gbit/s | Yes |
| BBIX Manila | 10 Gbit/s | Yes |
| BBIX Tokyo | 10 Gbit/s | Yes |
| BKNIX (Thailand): Bangkok | 100 Gbit/s | Yes |
| CNX: Internet Peering | 10 Gbit/s | Yes |
| DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN | 10 Gbit/s | Yes |
| Equinix Hong Kong | 100 Gbit/s | Yes |
| Equinix Singapore | 10 Gbit/s | No |
| France-IX Paris | 10 Gbit/s | Yes |
| HKIX: HKIX Peering LAN | 200 Gbit/s over 2 ports | Yes |
| IX Australia Sydney (NSW-IX): NSW-IX | 10 Gbit/s | Yes |
| JINX: JINX Peering | 10 Gbit/s | Yes |
| JKT-IX: Main | 10 Gbit/s | No |
| JPIX TOKYO | 10 Gbit/s | Yes |
| JPNAP Tokyo: Peering | 10 Gbit/s | Yes |
| KINX | 10 Gbit/s | Yes |
| KIXP - Nairobi: Peering LAN | 10 Gbit/s | Yes |
| LINX LON1: Main | 100 Gbit/s | Yes |
| MSK-IX Moscow: MSK-IX peering network | 10 Gbit/s | Yes |
| MyIX | 10 Gbit/s | Yes |
| NAPAfrica IX Johannesburg: Peering | 100 Gbit/s | Yes |
| NetIX: NetIX | 100 Gbit/s | Yes |
| SGIX: Peering LAN | 10 Gbit/s | Yes |
| SH-IX | 100 Gbit/s | Yes |
| SwissIX: Peering | 10 Gbit/s | Yes |
| THAILAND IX (TH-IX) | 10 Gbit/s | Yes |
| TPIX-TW | 10 Gbit/s | Yes |
| UAE-IX: UAE-IX Peering LAN | 100 Gbit/s | Yes |
From PeeringDB
Location from GeoLite2 data created by MaxMind