bgpreport

Network · data from 2026-11-12

AS216249 PHOTONSPARK

Registry name: PHOTONSPARK PHOTON SPARK SRL, RO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216249, 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.
2a01:e901:1::/48 Valid Nonecovered by 2a01:e901::/44 4 1%low visibility 4
81.181.245.0/24 Valid RIR databaseRIPE 669 99% 68
2a01:e901::/44 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS216249: AS216249:AS-PHOTONSPARK. 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 (AS216249 isn't in the set, or no route object for AS216249 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 objectsAS216249 in itNot covered
AS216249:AS-PHOTONSPARK RIPE 10243 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a01:e901:1::/48No route object for it. A route object for 2a01:e901::/44 with origin AS216249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS216249 in the RIR database for the space.4 of 636

Route objects not announced

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