bgpreport

Network · data from 2026-11-12

AS57999 DataNet ISP

Registry name: DATANETISP-AS LLC DataNet ISP, UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57999, 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.209.56.0/22 No ROA RIR databaseRIPE 671 100% 68
185.209.57.0/24 No ROA RIR databaseRIPE 670 100% 68
185.209.58.0/24 No ROA RIR databaseRIPE 670 100% 68
185.209.59.0/24 No ROA RIR databaseRIPE 670 100% 68
2a0b:42c0::/29 No ROA RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS57999: AS-DATANETISP. 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 (AS57999 isn't in the set, or no route object for AS57999 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 objectsAS57999 in itNot covered
AS-DATANETISP In no IRR database read today.

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

  • ROA: none5
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.209.56.0/22No ROA covers it. Add a ROA for AS57999, maxLength 22.671 of 673
ROA: none185.209.57.0/24No ROA covers it. Add a ROA for AS57999, maxLength 24.670 of 673
ROA: none185.209.58.0/24No ROA covers it. Add a ROA for AS57999, maxLength 24.670 of 673
ROA: none185.209.59.0/24No ROA covers it. Add a ROA for AS57999, maxLength 24.670 of 673
ROA: none2a0b:42c0::/29No ROA covers it. Add a ROA for AS57999, maxLength 29.633 of 636
AS-SET: not foundAS-DATANETISPPeeringDB names AS-DATANETISP; no IRR database read has it.

Route objects not announced

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

185.209.56.0/24RIPENo 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.