bgpreport

Network · data from 2026-11-12

AS49775 Volta-UK

Registry name: LunarDigital Volta Manchester Data Centres Limited, GB · PeeringDB

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

Announced routes

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

185.32.52.0/23 No ROA RIR databaseRIPE 672 100% 67
185.32.53.0/24 No ROA RIR databaseRIPE 672 100% 67
185.32.54.0/24 No ROA RIR databaseRIPE 672 100% 67
81.26.96.0/21 Valid RIR databaseRIPE 673 100% 67
185.194.252.0/23 Valid RIR databaseRIPE 673 100% 67
185.194.254.0/23 Valid RIR databaseRIPE 673 100% 67
45.15.40.0/24 Valid RIR databaseRIPE 672 100% 67
185.194.254.0/24 Valid RIR databaseRIPE 672 100% 67
2a0c:7d80::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS49775: RIPE::AS49775:AS-LUNAR-ALL. 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 (AS49775 isn't in the set, or no route object for AS49775 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 objectsAS49775 in itNot covered
RIPE::AS49775:AS-LUNAR-ALL RIPE 153103 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 6 are in fix.csv.

  • ROA: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none185.32.52.0/23No ROA covers it. Add a ROA for AS49775, maxLength 23.672 of 673
ROA: none185.32.53.0/24No ROA covers it. Add a ROA for AS49775, maxLength 24.672 of 673
ROA: none185.32.54.0/24No ROA covers it. Add a ROA for AS49775, maxLength 24.672 of 673

Route objects not announced

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

185.32.52.0/22RIPENo ROA
185.194.252.0/22RIPEValid
2a00:c2a0::/32RIPENo 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.