bgpreport

Network · data from 2026-11-12

AS202858 ALASTAIR

Registry name: ALASTAIR Alastair Barber, FI · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202858, 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.
44.30.104.0/24 No ROA Other IRR onlyRADB 673 100% 66
44.30.126.0/24 No ROA Other IRR onlyRADB 672 100% 66
2001:67c:16c8::/48 Valid Other origin only 636 100% 69
2001:67c:e8c::/48 Valid RIR databaseRIPE 636 100% 69
2001:67c:1908::/48 Valid RIR databaseRIPE 636 100% 69
2001:67c:298::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS202858: RIPE::AS202858:AS-ALASTAIR. 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 (AS202858 isn't in the set, or no route object for AS202858 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 objectsAS202858 in itNot covered
RIPE::AS202858:AS-ALASTAIR RIPE 115 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none44.30.104.0/24No ROA covers it. Add a ROA for AS202858, maxLength 24.673 of 673
Route object: RIR44.30.104.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none44.30.126.0/24No ROA covers it. Add a ROA for AS202858, maxLength 24.672 of 673
Route object: RIR44.30.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2001:67c:16c8::/48Route objects for it name AS206479. Add a route object with origin AS202858 in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS202858 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.