bgpreport

Network · data from 2026-11-12

AS8943 Jump Networks

Registry name: JUMP Jump Networks Ltd, GB · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 routes 83.3% RPKI valid · 83.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS8943, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS8943, 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.
::/0 bogon No ROA None 1 0%low visibility 1
185.73.44.0/22 Valid RIR databaseRIPE 673 100% 67
185.98.212.0/23 Valid RIR databaseRIPE 673 100% 67
194.33.11.0/24 Valid RIR databaseRIPE 673 100% 67
194.153.169.0/24 Valid RIR databaseRIPE 673 100% 67
203.11.114.0/24 Valid RIR databaseAPNIC 673 100% 67
212.13.192.0/19 Valid RIR databaseRIPE 673 100% 67
85.119.80.0/21 Valid RIR databaseRIPE 670 100% 67
2001:ba8::/32 Valid RIR databaseRIPE 635 100% 67
2001:baa::/32 Valid RIR databaseRIPE 635 100% 67
2a05:5a40::/32 Valid RIR databaseRIPE 635 100% 67
2a06:ec0::/32 Valid RIR databaseRIPE 635 100% 67
2a0a:1100::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS8943: RIPE::AS8943:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS8943 isn't in the set, or no route object for AS8943 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS8943 in itNot covered
RIPE::AS8943:AS-CUSTOMERS RIPElists itself further down2 member sets in no database: AS-HELIACAL, AS60223:AS-NETIFACE 3220689 Yes 1

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 6 are in fix.csv.

  • Bogon prefix1
  • AS-SET: missing member2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Bogon prefix::/0In IANA's special-purpose registry: default route.1 of 636
AS-SET: missing memberRIPE::AS8943:AS-CUSTOMERSAS8943:AS-CUSTOMERS (RIPE) lists AS-HELIACAL; no IRR database read has it.
AS-SET: missing memberRIPE::AS8943:AS-CUSTOMERSAS8943:AS-CUSTOMERS (RIPE) lists AS60223:AS-NETIFACE; no IRR database read has it.

Route objects not announced

Route objects with origin AS8943 whose prefix no peer sees AS8943 announce. Many are kept on purpose (backup routes, space announced only in some places).

83.138.62.0/24RIPEValid
2001:baf::/32RIPEValid
2a05:5a42::/32RIPEValid

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.