Network · data from 2026-11-12

AS20879 DIGI PT

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

8IPv4 routes 100.0% RPKI valid · 75.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS20879, seen from no peer

Announced routes

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


176.223.2.0/24	Valid	Nonecovered by 176.223.0.0/18	672 100%	67
176.223.3.0/24	Valid	Nonecovered by 176.223.0.0/18	672 100%	67
46.102.16.0/20	Valid	RIR databaseRIPE	672 100%	67
46.102.32.0/19	Valid	RIR databaseRIPE	672 100%	67
89.42.148.0/23	Valid	RIR databaseRIPE	672 100%	67
93.113.90.0/23	Valid	RIR databaseRIPE	672 100%	67
176.223.0.0/18	Valid	RIR databaseRIPE	672 100%	67
217.28.143.0/24	Valid	RIR databaseRIPE	672 100%	67
2a12:26c0::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

PeeringDB's irr_as_set for AS20879: AS20879:AS-DIGIPT. 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 (AS20879 isn't in the set, or no route object for AS20879 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.

Name	Database	ASNs	Sets	Route objects	AS20879 in it	Not covered
AS20879:AS-DIGIPT	RIPElists itself further down	26	8	3,291	Yes	0

Name

Database

ASNs

Sets

Route objects

AS20879 in it

Not covered

AS20879:AS-DIGIPT

RIPElists itself further down

3,291

Yes

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

Route object: none2

Change	Prefix or set	Detail	Full-table peers
Route object: none	176.223.2.0/24	No route object for it. A route object for 176.223.0.0/18 with origin AS20879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20879 in the RIR database for the space.	672 of 673
Route object: none	176.223.3.0/24	No route object for it. A route object for 176.223.0.0/18 with origin AS20879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20879 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

176.223.2.0/24

No route object for it. A route object for 176.223.0.0/18 with origin AS20879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20879 in the RIR database for the space.

672 of 673

Route object: none

176.223.3.0/24

672 of 673

Route objects not announced

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