bgpreport

Network · data from 2026-11-12

AS48506 Metical SRL

Registry name: METICAL-AS Metical SRL, MD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48506, 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.
178.76.64.0/21 Valid RIR databaseRIPE 671 100% 68
178.76.64.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.65.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.66.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.67.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.68.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.69.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.70.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.71.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.72.0/22 Valid RIR databaseRIPE 671 100% 68
178.76.72.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.73.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.74.0/24 Valid RIR databaseRIPE 671 100% 68
178.76.75.0/24 Valid RIR databaseRIPE 671 100% 68
185.163.192.0/22 Valid RIR databaseRIPE 671 100% 68
185.163.192.0/24 Valid RIR databaseRIPE 671 100% 68
185.163.193.0/24 Valid RIR databaseRIPE 671 100% 68
185.163.194.0/24 Valid RIR databaseRIPE 671 100% 68
185.163.195.0/24 Valid RIR databaseRIPE 671 100% 68
2a0a:2c00::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS48506's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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