bgpreport

Network · data from 2026-11-12

AS60907 MIRDARA-AS MIRDARA SRL

Registry name: MIRDARA-AS MIRDARA SRL, RO · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 50.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
1No 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 AS60907, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60907, 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.
89.36.174.0/24 Invalid: origin None 48 7%low visibility 28
188.241.32.0/22 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS60907 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin89.36.174.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS60907 should announce it, add a ROA for AS60907.48 of 673
Route object: none89.36.174.0/24No route object for it. Add a route object with origin AS60907 in the RIR database for the space.48 of 673
ROA: none188.241.32.0/22No ROA covers it. Add a ROA for AS60907, maxLength 22.673 of 673

Route objects not announced

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