bgpreport

Network · data from 2026-11-12

AS49289 MEDIA VENETO

Registry name: Media-Veneto Media Veneto SRL, IT · PeeringDB

25IPv4 routes 88.0% RPKI valid · 96.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS49289, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49289, 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.239.32.0/22 No ROA None 3 0%low visibility 3
193.200.48.0/24 No ROA RIR databaseRIPE 673 100% 67
193.200.49.0/24 No ROA RIR databaseRIPE 673 100% 67
62.100.74.0/24 Valid RIR databaseRIPE 673 100% 67
62.100.75.0/24 Valid RIR databaseRIPE 673 100% 67
62.100.81.0/24 Valid RIR databaseRIPE 673 100% 67
93.185.112.0/20 Valid RIR databaseRIPE 673 100% 67
159.255.136.0/22 Valid RIR databaseRIPE 673 100% 67
159.255.144.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.232.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.233.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.234.0/24 Valid RIR databaseRIPE 673 100% 67
171.22.235.0/24 Valid RIR databaseRIPE 673 100% 67
178.239.36.0/24 Valid RIR databaseRIPE 673 100% 67
178.239.40.0/22 Valid RIR databaseRIPE 673 100% 67
178.239.44.0/23 Valid RIR databaseRIPE 673 100% 67
178.239.46.0/23 Valid RIR databaseRIPE 673 100% 67
185.63.132.0/23 Valid RIR databaseRIPE 673 100% 67
185.63.135.0/24 Valid RIR databaseRIPE 673 100% 67
188.94.120.0/21 Valid RIR databaseRIPE 673 100% 67
193.200.26.0/24 Valid RIR databaseRIPE 673 100% 67
193.200.27.0/24 Valid RIR databaseRIPE 673 100% 67
178.239.32.0/24 Valid RIR databaseRIPE 670 100% 67
178.239.34.0/24 Valid RIR databaseRIPE 670 100% 67
178.239.35.0/24 Valid RIR databaseRIPE 670 100% 67
2a00:c50::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS49289: AS-IPROUTE-SET. 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 (AS49289 isn't in the set, or no route object for AS49289 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 objectsAS49289 in itNot covered
AS-IPROUTE-SET RIPElists itself further down 5113566 Yes 1

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

  • ROA: none3
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none178.239.32.0/22No ROA covers it. Add a ROA for AS49289, maxLength 22.3 of 673
Route object: none178.239.32.0/22No route object for it. Add a route object with origin AS49289 in the RIR database for the space.3 of 673
ROA: none193.200.48.0/24No ROA covers it. Add a ROA for AS49289, maxLength 24.673 of 673
ROA: none193.200.49.0/24No ROA covers it. Add a ROA for AS49289, maxLength 24.673 of 673

Route objects not announced

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