bgpreport

Network · data from 2026-11-12

AS44418 Bitdefender

Registry name: BITDEFENDER-AS Bitdefender SRL, RO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44418, 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.43.193.0/29 Invalid: origin None 0 0%low visibility 2
91.199.104.0/24 Valid RIR databaseRIPE 673 100% 66
91.220.75.0/24 Valid RIR databaseRIPE 673 100% 66
195.189.155.0/24 Valid RIR databaseRIPE 673 100% 66
195.210.4.0/24 Valid RIR databaseRIPE 673 100% 66
195.210.5.0/24 Valid RIR databaseRIPE 673 100% 66
81.161.59.0/24 Valid RIR databaseRIPE 672 100% 66
2001:67c:1438::/48 Valid RIR databaseRIPE 636 100% 67
2001:67c:eb4::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS44418's PeeringDB record names no 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
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin89.43.193.0/29ROAs covering it name AS39737, not AS44418. If AS44418 should announce it, add a ROA for AS44418.0 of 673
Route object: none89.43.193.0/29No route object for it. Add a route object with origin AS44418 in the RIR database for the space.0 of 673

Route objects not announced

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

195.210.4.0/23RIPEValid

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.