bgpreport

Network · data from 2026-11-12

AS43950 Spilsby Internet Solutions

Registry name: SPILSBY-AS Terence Froy trading as "Spilsby Internet Solutions", GB · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% 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
4Route objects not announced registered with origin AS43950, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43950, 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.

79.98.32.0/21 No ROA None 2 0%low visibility 2
193.239.8.0/22 Valid RIR databaseRIPE 672 100% 67
2a01:568::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS43950: AS-SPILSBY. 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 (AS43950 isn't in the set, or no route object for AS43950 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 objectsAS43950 in itNot covered
AS-SPILSBY RIPElists itself further down 3311 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.

  • ROA: none1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none79.98.32.0/21No ROA covers it. Add a ROA for AS43950, maxLength 21.2 of 673
Route object: none79.98.32.0/21No route object for it. Add a route object with origin AS43950 in the RIR database for the space.2 of 673

Route objects not announced

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

2a01:568::/36RIPEValid
2a01:568:3000::/36RIPEValid
2a01:568:4000::/36RIPEValid
2a01:568:5000::/36RIPEValid

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.