Routing security
AS43950 SPILSBY-AS
Unclassified RIPE Content
Announcements
What this network originates
Every prefix observed with AS43950 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a01:568::/32 | RPKI valid | IRR | 29 |
| 193.239.8.0/22 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS43950 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 193.239.8.0/22 | /22 | RIPENCC |
| 2a01:568::/32 | /32 | RIPENCC |
| 2a01:568::/36 | /36 | RIPENCC |
| 2a01:568:3000::/36 | /36 | RIPENCC |
| 2a01:568:4000::/36 | /36 | RIPENCC |
| 2a01:568:5000::/36 | /36 | RIPENCC |
| 2a01:568:6000::/36 | /36 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS8943 | Jump Networks Ltd | Declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS43950 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 2a01:568::/36 | RIPE | Spilsby Internet Solutions - Anycast | SPILSBY-MNT | 2017-09-20 | Not announced |
| 2a01:568:3000::/36 | RIPE | Spilsby Internet Solutions | SPILSBY-MNT | 2012-11-21 | Not announced |
| 2a01:568:4000::/36 | RIPE | Spilsby Internet Solutions - London Telehouse | SPILSBY-MNT | 2017-09-24 | Not announced |
| 2a01:568:5000::/36 | RIPE | Spilsby Internet Solutions - IP House | SPILSBY-MNT | 2025-06-28 | Not announced |
| 193.239.8.0/22 | RIPE | Spilsby Internet Solutions | SPILSBY-MNT | 2022-07-10 | Announced |
| 2a01:568::/32 | RIPE | Spilsby Internet Solutions | SPILSBY-MNT | 2013-07-25 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS43950 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-SPILSBY | PeeringDB | Declared by the operator as its own set |
AS-C4L | RIPE | Lists AS43950 as a direct member |
AS-GOSCOMB-V6 | RIPE | Lists AS43950 as a direct member |
AS-KEWLIO-V6 | RIPE | Lists AS43950 as a direct member |
AS-SPILSBY | RIPE | Lists AS43950 as a direct member |
AS-TELECITYGROUP-UK | RIPE | Lists AS43950 as a direct member |
AS-UKGRID | RIPE | Lists AS43950 as a direct member |
AS8943:AS-CUSTOMERS | RIPE | Lists AS43950 as a direct member |
RPKI from rpki-client, validated 2026-10-26 12:04 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-26. Cross-check on bgp.he.net.