bgpreport

Network · data from 2026-11-12

AS212109 Squirrel Internet

Registry name: SQUIRREL Squirrel Internet Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212109, 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.
38.79.120.0/22 No ROA Other IRR onlyRADB 671 100% 67
154.49.80.0/22 No ROA Other IRR onlyRADB 671 100% 67
154.49.120.0/22 No ROA Other IRR onlyRADB 671 100% 67
154.56.238.0/23 No ROA Other IRR onlyRADB 671 100% 67
154.56.252.0/23 No ROA Other IRR onlyRADB 671 100% 67
23.230.54.0/23 Valid Other IRR onlyRADB 671 100% 67
5.59.182.0/24 Valid RIR databaseRIPE 671 100% 67
5.59.241.0/24 Valid RIR databaseRIPE 671 100% 67
45.39.82.0/23 Valid RIR databaseARIN, RADB 671 100% 67
45.9.20.0/24 Valid RIR databaseRIPE 670 100% 67
2a10:8701::/32 Valid RIR databaseRIPE 634 100% 67
2a10:8702::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS212109: AS-SQUIRREL. 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 (AS212109 isn't in the set, or no route object for AS212109 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 objectsAS212109 in itNot covered
AS-SQUIRREL RIPE 2115 Yes 0

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

  • ROA: none5
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none38.79.120.0/22No ROA covers it. Add a ROA for AS212109, maxLength 22.671 of 673
Route object: RIR38.79.120.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.49.80.0/22No ROA covers it. Add a ROA for AS212109, maxLength 22.671 of 673
Route object: RIR154.49.80.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.49.120.0/22No ROA covers it. Add a ROA for AS212109, maxLength 22.671 of 673
Route object: RIR154.49.120.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.56.238.0/23No ROA covers it. Add a ROA for AS212109, maxLength 23.671 of 673
Route object: RIR154.56.238.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.56.252.0/23No ROA covers it. Add a ROA for AS212109, maxLength 23.671 of 673
Route object: RIR154.56.252.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR23.230.54.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS212109 is announced.

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.