Data as of Nov 7, 2026
212.9.16.0/24
No anonymizer space · no proxy exits in 30 daysJT (Jersey) Limited
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.9.0.0/19 since May 2005 | AS8681 | Residential | 32 2 always on | JT (Jersey) Limited |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.9.0.0/19 | 8,192 | JE-JERSEYTELECOM-980318 | JT (Jersey) Limited (ORG-JT7-RIPE) · JE | ALLOCATED PA | Dec 17, 2001 | ripe@ |
| └ 212.9.16.0/24 | 256 | Index_ | unknown | LIR-PARTITIONED PA | Apr 17, 2024 | ripe@ via JE-JERSEYTELECOM-980318 |
| └ 212.9.16.0/30 | 4 | Sanne | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.4/30 | 4 | Index_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.8/30 | 4 | Health_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.12/30 | 4 | Stonehage_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.16/31 | 2 | SDWAN_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.18/31 | 2 | SDWAN_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.20/30 | 4 | Ekit_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.24/30 | 4 | Tayana | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.28/31 | 2 | SDWAN | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.30/31 | 2 | JTG_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.32/31 | 2 | JTG_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.34/31 | 2 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.36/30 | 4 | SoJ_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.48/31 | 2 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.52/30 | 4 | WorldStone_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.56/30 | 4 | Foreshore_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.60/30 | 4 | Mobility_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.64/30 | 4 | LTE | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.68/30 | 4 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.72/29 | 8 | R_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.80/30 | 4 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.84/30 | 4 | Trial_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.88/30 | 4 | Trial_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.92/30 | 4 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.96/30 | 4 | JT_ | unknown | ASSIGNED PA | Apr 17, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.100/30 | 4 | Franklin_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.104/29 | 8 | Appleby_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.112/30 | 4 | OOB_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.132/30 | 4 | Regus_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.136/30 | 4 | Siphon | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.148/30 | 4 | Worldstone_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.152/29 | 8 | Business_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.160/29 | 8 | JFSC | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.168/29 | 8 | JFSC | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.176/31 | 2 | Jersey_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.180/31 | 2 | Jamie_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.184/31 | 2 | Health_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.190/31 | 2 | JT_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.192/29 | 8 | Perdurance | unknown | ASSIGNED PA | May 16, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.200/29 | 8 | G4S | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.208/30 | 4 | Elian | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.212/30 | 4 | Elian | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.216/30 | 4 | Jersey_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.220/30 | 4 | Sandpiper_ | unknown | ASSIGNED PA | Apr 18, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.224/29 | 8 | C5_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
| └ 212.9.16.248/29 | 8 | DDOS_ | unknown | ASSIGNED PA | May 7, 2024 | ripe@ via Index_Venture_Associates |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
256 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 184 | 72% | 42 | |
| Residential | 64 | 25% | 9 | |
| Mobile | 8 | 3.1% | 2 |
Network & registry
Registry
Holder
- Organization
- JT (Jersey) Limited
- Handle
- ORG-JT7-RIPE
- Range
- 212.
9. 0. 0/ 19 - Registration type
- ALLOCATED PA
- Record created
- Dec 17, 2001
- Reallocated to
- Not named in the registry
- Reallocated range
- 212.
9. 16. 0/ 24 - Reallocation type
- LIR-PARTITIONED PA
- Reallocated
- Apr 17, 2024
Origin network
AS8681
JE
- Name
- JT (Jersey) Limited
- Type
- Internet provider
- Registered
- Feb 20, 1998
- Domain
- jtglobal.com
- Website
- jtglobal.com
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Nov 2020
- Current origin since
- Nov 2020 · 6.0 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.9.16.0/24 | AS8681 | /24 | RIPE | RPKI valid |
| 212.9.0.0/19 | AS8681 | /19 | RIPE | Too specific |
Whois
Registration for this announcement
- Range
- 212.
9. 16. 0/ 24 - Netname
- Index_
Venture_ Associates - Registrant country
- JE
- Organization
- Not stated by the registry
- Type
- LIR-PARTITIONED PA
- Created
- Apr 17, 2024
- Updated
- Apr 17, 2024
- Maintainer
- JE-TEL-MNT
- RIR
- RIPE NCC
- Country
- JE
- Delegated
- Mar 18, 1998
- Status
- assigned
Report abuse
Abuse contact
- ripe@
jtglobal. com - Name
- Abuse-C Role
- Handle
- AR15929-RIPE