Autonomous system
AS8943 JUMP
Hosting RIPE
Summary
Jump Networks
hosting colocation transit legacy
JUMP is Jump Networks Ltd, a long-running British provider of IP bandwidth and server colocation, operating out of IP House and Telehouse North in London Docklands. The company is registered in Cambridge and has been trading since 2000.
What it's used for
- Colocation and hosting. The rDNS across its own
212.13.192.0/19,185.73.44.0/22and185.98.212.0/23mixes Jump's own infrastructure (gateway.jump.net.uk,ntp1.jump.net.uk,vrrp1.jump.net.uk) with customer machines named on their own domains — small UK businesses, news servers and other service operators. - Transit for downstream networks. It originates
85.119.80.0/21, which is registered to BitFolk Limited, the London VPS provider (*.bitfolk.com), on BitFolk's own behalf. That is a customer's provider-independent space, not Jump's.
Notable
- Heavily peered for its size: roughly 12,500 IPv4 addresses but around a hundred BGP neighbours, reflecting an open peering policy at the London exchanges. Address count is a poor proxy for the importance of a network like this.
- Both kinds of space sit under the same AS, so individual prefixes must be attributed to their registrant rather than blanket-assigned to Jump.
Interesting
- Among its prefixes is
203.11.114.0/24, APNIC space whose rDNS readsgw.uk.apana.auandmail.uk.apana.org.au— the UK presence of APANA, the Australian Public Access Network Association, an early volunteer-run network. A fragment of 1990s community networking still routed out of a London datacentre.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Address space
Summary
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 12 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS8943- Registry name
- JUMP
- Registrant
- JUMP-MNT
- Abuse contact
- abuse@jump.net.uk
- Registered
- 2002-07-04
- Last changed
- 2026-03-12
- Status
- active
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
No IC3 indicators Nothing from the FBI IC3 feed.
Threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere