bgpreport

Network · data from 2026-11-12

AS25311 DIGI BE

Registry name: DIGI-BE DIGI ROMANIA S.A., RO · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS25311, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25311, 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.
46.102.0.0/20 Valid RIR databaseRIPE 672 100% 67
86.105.206.0/23 Valid RIR databaseRIPE 672 100% 67
89.34.180.0/22 Valid RIR databaseRIPE 672 100% 67
89.47.208.0/20 Valid RIR databaseRIPE 672 100% 67
94.176.200.0/21 Valid RIR databaseRIPE 672 100% 67
188.209.96.0/20 Valid RIR databaseRIPE 672 100% 67
195.182.220.0/23 Valid RIR databaseRIPE 670 100% 67
2a01:4700:8000::/33 Valid RIR databaseRIPE 635 100% 67
2a03:9c20:2002::/48 Valid RIR databaseRIPE 635 100% 67
2a03:9c20:3000::/36 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS25311: AS25311:AS-DIGIBE. 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 (AS25311 isn't in the set, or no route object for AS25311 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 objectsAS25311 in itNot covered
AS25311:AS-DIGIBE RIPE 3247 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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