bgpreport

Network · data from 2026-11-12

AS49687 REQ RoSite Equipment SRL

Registry name: REQ RoSite Equipment SRL, RO · not in PeeringDB

9IPv4 routes 88.9% RPKI valid · 88.9% with a route object
1IPv6 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
3Route objects not announced registered with origin AS49687, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49687, 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.
188.74.191.0/24 Invalid: origin Other origin only 33 5%low visibility 20
5.157.136.0/21 Valid RIR databaseRIPE 671 100% 68
5.157.144.0/21 Valid RIR databaseRIPE 671 100% 68
5.157.224.0/22 Valid RIR databaseRIPE 671 100% 68
37.35.44.0/22 Valid RIR databaseRIPE 671 100% 68
146.66.216.0/23 Valid RIR databaseRIPE 671 100% 68
178.157.127.0/24 Valid RIR databaseRIPE 671 100% 68
188.74.170.0/24 Valid RIR databaseRIPE 671 100% 68
188.119.176.0/22 Valid RIR databaseRIPE 671 100% 68
2a03:8800::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin188.74.191.0/24ROAs covering it name AS212192, not AS49687. If AS49687 should announce it, add a ROA for AS49687.33 of 673
Route object: none188.74.191.0/24Route objects for it name AS212192. Add a route object with origin AS49687 in the RIR database for the space.33 of 673

Route objects not announced

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

5.157.137.0/24RIPEValid
5.157.138.0/24RIPEValid
5.157.140.0/22RIPEValid

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.