Network · data from 2026-11-12

AS51007 mediapro-as Servicios Audiovisuales Overon S.L.

Registry name: mediapro-as Servicios Audiovisuales Overon S.L., ES · not in PeeringDB

25IPv4 routes 100.0% RPKI valid · 60.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 10 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

5Route objects not announced registered with origin AS51007, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51007, 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.


80.84.158.0/24	Valid	Other origin only	672 100%	67
80.84.128.0/21	Valid	Other origin only	671 100%	67
80.84.135.0/24	Valid	Other origin only	671 100%	67
80.84.148.0/24	Valid	Other origin only	671 100%	67
80.84.150.0/23	Valid	Other origin only	276 41%	63
80.84.152.0/22	Valid	Other origin only	276 41%	63
80.84.156.0/23	Valid	Other origin only	204 30%	56
178.249.8.0/22	Valid	None	201 30%	56
80.84.158.0/23	Valid	Other origin only	97 14%	48
178.249.14.0/23	Valid	Nonecovered by 178.249.12.0/22	2 0%low visibility	2
178.249.8.0/24	Valid	RIR databaseRIPE	672 100%	67
178.249.10.0/24	Valid	RIR databaseRIPE	672 100%	67
185.100.180.0/24	Valid	RIR databaseRIPE	672 100%	67
185.100.181.0/24	Valid	RIR databaseRIPE	672 100%	67
185.100.182.0/24	Valid	RIR databaseRIPE	672 100%	67
185.100.183.0/24	Valid	RIR databaseRIPE	672 100%	67
178.249.9.0/24	Valid	RIR databaseRIPE	671 100%	67
178.249.12.0/24	Valid	RIR databaseRIPE	671 100%	67
185.100.182.0/23	Valid	RIR databaseRIPE	671 100%	67
178.249.14.0/24	Valid	RIR databaseRIPE	651 97%	67
178.249.15.0/24	Valid	RIR databaseRIPE	630 94%	67
31.187.68.0/24	Valid	RIR databaseRIPE	234 35%	59
178.249.11.0/24	Valid	RIR databaseRIPE	207 31%	56
178.249.12.0/22	Valid	RIR databaseRIPE	202 30%	56
178.249.13.0/24	Valid	RIR databaseRIPE	23 3%low visibility	15

80.84.158.0/24

Valid

Other origin only

672 100%

80.84.128.0/21

Valid

Other origin only

671 100%

80.84.135.0/24

Valid

Other origin only

671 100%

80.84.148.0/24

Valid

Other origin only

671 100%

80.84.150.0/23

Valid

Other origin only

276 41%

80.84.152.0/22

Valid

Other origin only

276 41%

80.84.156.0/23

Valid

Other origin only

204 30%

178.249.8.0/22

Valid

None

201 30%

80.84.158.0/23

Valid

Other origin only

97 14%

178.249.14.0/23

Valid

Nonecovered by 178.249.12.0/22

2 0%low visibility

178.249.8.0/24

Valid

RIR databaseRIPE

672 100%

178.249.10.0/24

Valid

RIR databaseRIPE

672 100%

185.100.180.0/24

Valid

RIR databaseRIPE

672 100%

185.100.181.0/24

Valid

RIR databaseRIPE

672 100%

185.100.182.0/24

Valid

RIR databaseRIPE

672 100%

185.100.183.0/24

Valid

RIR databaseRIPE

672 100%

178.249.9.0/24

Valid

RIR databaseRIPE

671 100%

178.249.12.0/24

Valid

RIR databaseRIPE

671 100%

185.100.182.0/23

Valid

RIR databaseRIPE

671 100%

178.249.14.0/24

Valid

RIR databaseRIPE

651 97%

178.249.15.0/24

Valid

RIR databaseRIPE

630 94%

31.187.68.0/24

Valid

RIR databaseRIPE

234 35%

178.249.11.0/24

Valid

RIR databaseRIPE

207 31%

178.249.12.0/22

Valid

RIR databaseRIPE

202 30%

178.249.13.0/24

Valid

RIR databaseRIPE

23 3%low visibility

AS-SET

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

Route object: none10
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	80.84.158.0/24	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	672 of 673
Route object: none	80.84.128.0/21	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	671 of 673
Route object: none	80.84.135.0/24	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	671 of 673
Route object: none	80.84.148.0/24	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	671 of 673
Route object: none	80.84.150.0/23	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	276 of 673
Route object: none	80.84.152.0/22	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	276 of 673
Route object: none	80.84.156.0/23	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	204 of 673
Route object: none	178.249.8.0/22	No route object for it. Add a route object with origin AS51007 in the RIR database for the space.	201 of 673
Route object: none	80.84.158.0/23	Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.	97 of 673
Route object: none	178.249.14.0/23	No route object for it. A route object for 178.249.12.0/22 with origin AS51007 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51007 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

80.84.158.0/24

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

672 of 673

Route object: none

80.84.128.0/21

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

671 of 673

Route object: none

80.84.135.0/24

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

671 of 673

Route object: none

80.84.148.0/24

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

671 of 673

Route object: none

80.84.150.0/23

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

276 of 673

Route object: none

80.84.152.0/22

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

276 of 673

Route object: none

80.84.156.0/23

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

204 of 673

Route object: none

178.249.8.0/22

No route object for it. Add a route object with origin AS51007 in the RIR database for the space.

201 of 673

Route object: none

80.84.158.0/23

Route objects for it name AS21057. Add a route object with origin AS51007 in the RIR database for the space.

97 of 673

Route object: none

178.249.14.0/23

No route object for it. A route object for 178.249.12.0/22 with origin AS51007 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51007 in the RIR database for the space.

2 of 673

Route objects not announced

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


80.84.138.0/23	RIPE	Invalid: origin
80.84.138.0/24	RIPE	Invalid: origin
80.84.139.0/24	RIPE	Invalid: origin
178.249.10.0/23	RIPE	Invalid: maxLength
2a03:a420::/32	RADB	No ROA

80.84.138.0/23

RIPE

Invalid: origin

80.84.138.0/24

RIPE

Invalid: origin

80.84.139.0/24

RIPE

Invalid: origin

178.249.10.0/23

RIPE

Invalid: maxLength

2a03:a420::/32

RADB

No ROA

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.