bgpreport

Network · data from 2026-11-12

AS48803 MEDIATEKNIK Mediateknik i Varberg AB

Registry name: MEDIATEKNIK Mediateknik i Varberg AB, SE · not in PeeringDB

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

Announced routes

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

148.160.239.0/24 No ROA RIR databaseRIPE 672 100% 66
91.217.186.0/24 No ROA RIR databaseRIPE 671 100% 66
185.19.248.0/22 No ROA RIR databaseRIPE 671 100% 66
185.67.56.0/22 No ROA RIR databaseRIPE 671 100% 66
217.73.96.0/20 No ROA RIR databaseRIPE 671 100% 66
2001:67c:22e0::/48 No ROA RIR databaseRIPE 634 100% 67
2a00:c740::/32 No ROA RIR databaseRIPE 634 100% 67
2001:67c:2ddc::/48 Valid None 634 100% 67
193.183.250.0/24 Valid RIR databaseRIPE 672 100% 67
31.24.72.0/21 Valid RIR databaseRIPE 671 100% 66
88.206.160.0/20 Valid RIR databaseRIPE 671 100% 66
88.206.176.0/22 Valid RIR databaseRIPE 671 100% 66
94.103.192.0/20 Valid RIR databaseRIPE 671 100% 66
185.27.164.0/22 Valid RIR databaseRIPE 671 100% 66
192.71.221.0/24 Valid RIR databaseRIPE 671 100% 66
193.183.148.0/22 Valid RIR databaseRIPE 671 100% 66
194.68.117.0/24 Valid RIR databaseRIPE 671 100% 66
194.132.228.0/22 Valid RIR databaseRIPE 671 100% 66
2a01:8e00::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none148.160.239.0/24No ROA covers it. Add a ROA for AS48803, maxLength 24.672 of 673
ROA: none91.217.186.0/24No ROA covers it. Add a ROA for AS48803, maxLength 24.671 of 673
ROA: none185.19.248.0/22No ROA covers it. Add a ROA for AS48803, maxLength 22.671 of 673
ROA: none185.67.56.0/22No ROA covers it. Add a ROA for AS48803, maxLength 22.671 of 673
ROA: none217.73.96.0/20No ROA covers it. Add a ROA for AS48803, maxLength 20.671 of 673
ROA: none2001:67c:22e0::/48No ROA covers it. Add a ROA for AS48803, maxLength 48.634 of 636
ROA: none2a00:c740::/32No ROA covers it. Add a ROA for AS48803, maxLength 32.634 of 636
Route object: none2001:67c:2ddc::/48No route object for it. Add a route object with origin AS48803 in the RIR database for the space.634 of 636

Route objects not announced

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

217.73.96.0/21RIPENo ROA
217.73.104.0/22RIPENo ROA
217.73.108.0/22RIPENo 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.