bgpreport

Network · data from 2026-11-12

AS214929 LastResponse

Registry name: LastResponse Lukas Wenzl trading as LastResponse, AT · PeeringDB

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

Announced routes

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

2a06:9f41:300::/40 Invalid: origin None 1 0%low visibility 1
2a06:9f41:500::/40 Invalid: origin None 1 0%low visibility 1
2a06:9f41:900::/40 Invalid: origin None 1 0%low visibility 1
154.208.114.0/24 Invalid: origin RIR databaseAFRINIC 132 20% 51
2a0f:85c1:cd5::/48 No ROA RIR databaseRIPE 636 100% 69
94.249.228.0/24 Valid RIR databaseRIPE 673 100% 66
2602:f9ba:b1::/48 Valid RIR databaseARIN 636 100% 69
2a0b:4e07:39::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:85c1:c50::/44 Valid RIR databaseRIPE 636 100% 69
2a13:9500:63::/48 Valid RIR databaseRIPE 636 100% 69
2a13:9500:96::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS214929: AS214929:AS-MAIN. 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 (AS214929 isn't in the set, or no route object for AS214929 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 objectsAS214929 in itNot covered
AS214929:AS-MAIN RIPE 118 Yes 3

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

  • ROA: origin4
  • ROA: none1
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin2a06:9f41:300::/40ROAs covering it name AS215085, not AS214929. If AS214929 should announce it, add a ROA for AS214929.1 of 636
Route object: none2a06:9f41:300::/40No route object for it. Add a route object with origin AS214929 in the RIR database for the space.1 of 636
ROA: origin2a06:9f41:500::/40ROAs covering it name AS215085, not AS214929. If AS214929 should announce it, add a ROA for AS214929.1 of 636
Route object: none2a06:9f41:500::/40No route object for it. Add a route object with origin AS214929 in the RIR database for the space.1 of 636
ROA: origin2a06:9f41:900::/40ROAs covering it name AS215085, not AS214929. If AS214929 should announce it, add a ROA for AS214929.1 of 636
Route object: none2a06:9f41:900::/40No route object for it. Add a route object with origin AS214929 in the RIR database for the space.1 of 636
ROA: origin154.208.114.0/24ROAs covering it name AS17561, not AS214929. If AS214929 should announce it, add a ROA for AS214929.132 of 673
ROA: none2a0f:85c1:cd5::/48No ROA covers it. Add a ROA for AS214929, maxLength 48.636 of 636

Route objects not announced

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