bgpreport

Network · data from 2026-11-12

AS44024 Radu Draghici

Registry name: RO-RADUDRAGHICI Radu Draghici, RO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44024, 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.
2a06:de00:7000::/44 No ROA None 462 73% 64
44.32.167.0/24 No ROA Other IRR onlyRADB 671 100% 67
2a0e:b107:23::/48 No ROA RIR databaseRIPE 635 100% 67
2a05:91c3::/48 Valid None 635 100% 67
185.225.207.0/24 Valid RIR databaseRIPE 671 100% 67
2a0f:85c1:cf0::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS44024: AS-RADUDRAGHICI. 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 (AS44024 isn't in the set, or no route object for AS44024 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 objectsAS44024 in itNot covered
AS-RADUDRAGHICI RIPE 216 Yes 2

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: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a06:de00:7000::/44No ROA covers it. Add a ROA for AS44024, maxLength 44.462 of 636
Route object: none2a06:de00:7000::/44No route object for it. Add a route object with origin AS44024 in the RIR database for the space.462 of 636
ROA: none44.32.167.0/24No ROA covers it. Add a ROA for AS44024, maxLength 24.671 of 673
Route object: RIR44.32.167.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2a0e:b107:23::/48No ROA covers it. Add a ROA for AS44024, maxLength 48.635 of 636
Route object: none2a05:91c3::/48No route object for it. Add a route object with origin AS44024 in the RIR database for the space.635 of 636

Route objects not announced

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

44.182.25.0/24ALTDBNo 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.