bgpreport

Network · data from 2026-11-12

AS209910 MAPEKA

Registry name: MARKETING DITT REDMOVIL SL, ES · PeeringDB

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

Announced routes

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

185.236.248.0/22 Valid None 673 100% 67
5.252.94.0/23 Valid Nonecovered by 5.252.92.0/22 670 100% 67
45.65.64.0/22 Valid Other origin only 670 100% 67
5.252.93.0/24 Valid RIR databaseRIPE 673 100% 67
185.200.76.0/22 Valid RIR databaseRIPE 673 100% 67
185.200.76.0/24 Valid RIR databaseRIPE 673 100% 67
185.200.78.0/24 Valid RIR databaseRIPE 673 100% 67
185.200.79.0/24 Valid RIR databaseRIPE 673 100% 67
185.236.248.0/24 Valid RIR databaseRIPE 673 100% 67
185.236.249.0/24 Valid RIR databaseRIPE 673 100% 67
185.236.250.0/24 Valid RIR databaseRIPE 673 100% 67
185.236.251.0/24 Valid RIR databaseRIPE 673 100% 67
193.84.48.0/23 Valid RIR databaseRIPE 673 100% 67
193.84.48.0/24 Valid RIR databaseRIPE 673 100% 67
193.84.49.0/24 Valid RIR databaseRIPE 673 100% 67
193.84.92.0/24 Valid RIR databaseRIPE 673 100% 67
193.84.93.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS209910'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 13 are in fix.csv.

  • Route object: none3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none185.236.248.0/22No route object for it. Add a route object with origin AS209910 in the RIR database for the space.673 of 673
Route object: none5.252.94.0/23No route object for it. A route object for 5.252.92.0/22 with origin AS209910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209910 in the RIR database for the space.670 of 673
Route object: none45.65.64.0/22Route objects for it name AS51487. Add a route object with origin AS209910 in the RIR database for the space.670 of 673

Route objects not announced

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

5.252.92.0/22RIPENo ROA
5.252.92.0/24RIPEValid
5.252.94.0/24RIPEInvalid: maxLength
5.252.95.0/24RIPEInvalid: maxLength
45.65.64.0/24RIPEInvalid: maxLength
45.65.65.0/24RIPEInvalid: maxLength
45.65.66.0/24RIPEInvalid: maxLength
45.65.67.0/24RIPEInvalid: maxLength
185.200.77.0/24RIPEInvalid: maxLength
193.84.92.0/23RIPENo 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.