bgpreport

Network · data from 2026-11-12

AS49823 Hastingwood Securities

Registry name: Hastingwood Hastingwood Securities Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49823, 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.
109.72.208.0/20 Valid RIR databaseRIPE 673 100% 67
109.72.210.0/24 Valid RIR databaseRIPE 673 100% 67
194.1.180.0/24 Valid RIR databaseRIPE 673 100% 67
109.72.208.0/21 Valid RIR databaseRIPE 374 56% 63
109.72.208.0/24 Valid RIR databaseRIPE 374 56% 63
109.72.209.0/24 Valid RIR databaseRIPE 374 56% 63
109.72.211.0/24 Valid RIR databaseRIPE 374 56% 63
109.72.213.0/24 Valid RIR databaseRIPE 374 56% 63
109.72.216.0/21 Valid RIR databaseRIPE 374 56% 63
109.72.219.0/24 Valid RIR databaseRIPE 374 56% 63
109.72.212.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.214.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.215.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.217.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.218.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.220.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.221.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.222.0/24 Valid RIR databaseRIPE 371 55% 63
109.72.223.0/24 Valid RIR databaseRIPE 371 55% 63

AS-SET

PeeringDB's irr_as_set for AS49823: RIPE::AS-HASTINGWOOD. 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 (AS49823 isn't in the set, or no route object for AS49823 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 objectsAS49823 in itNot covered
RIPE::AS-HASTINGWOOD RIPE 1123 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 4 are in fix.csv.

  • Route object: not announced4

Route objects not announced

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

109.72.208.0/22RIPEInvalid: maxLength
109.72.212.0/22RIPEInvalid: maxLength
109.72.216.0/22RIPEInvalid: maxLength
2a07:840::/29RIPENo ROA

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.