bgpreport

Network · data from 2026-11-12

AS34244 Teleservice Bredband Skåne AB

Registry name: TELESERVICE Teleservice Bredband Skane AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34244, 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.253.60.0/24 No ROA RIR databaseRIPE 671 100% 67
193.42.21.0/24 No ROA RIR databaseRIPE 671 100% 67
31.170.24.0/21 Valid RIR databaseRIPE 673 100% 67
85.30.128.0/18 Valid RIR databaseRIPE 673 100% 67
92.39.32.0/20 Valid RIR databaseRIPE 673 100% 67
128.127.184.0/21 Valid RIR databaseRIPE 673 100% 67
155.137.24.0/21 Valid RIR databaseRIPE 673 100% 67
178.236.64.0/20 Valid RIR databaseRIPE 673 100% 67
5.180.0.0/22 Valid RIR databaseRIPE 671 100% 67
37.221.104.0/22 Valid RIR databaseRIPE 671 100% 67
45.8.152.0/22 Valid RIR databaseRIPE 671 100% 67
45.14.4.0/22 Valid RIR databaseRIPE 671 100% 67
45.93.232.0/22 Valid RIR databaseRIPE 671 100% 67
45.131.188.0/22 Valid RIR databaseRIPE 671 100% 67
45.152.172.0/22 Valid RIR databaseRIPE 671 100% 67
81.92.196.0/22 Valid RIR databaseRIPE 671 100% 67
81.92.220.0/22 Valid RIR databaseRIPE 671 100% 67
94.46.136.0/22 Valid RIR databaseRIPE 671 100% 67
94.46.240.0/22 Valid RIR databaseRIPE 671 100% 67
141.98.236.0/22 Valid RIR databaseRIPE 671 100% 67
178.255.112.0/22 Valid RIR databaseRIPE 671 100% 67
185.4.8.0/22 Valid RIR databaseRIPE 671 100% 67
185.27.96.0/22 Valid RIR databaseRIPE 671 100% 67
185.121.44.0/22 Valid RIR databaseRIPE 671 100% 67
185.176.28.0/22 Valid RIR databaseRIPE 671 100% 67
185.186.32.0/22 Valid RIR databaseRIPE 671 100% 67
185.197.224.0/22 Valid RIR databaseRIPE 671 100% 67
185.216.152.0/22 Valid RIR databaseRIPE 671 100% 67
185.223.236.0/22 Valid RIR databaseRIPE 671 100% 67
185.240.208.0/22 Valid RIR databaseRIPE 671 100% 67
185.247.236.0/22 Valid RIR databaseRIPE 671 100% 67
188.66.48.0/22 Valid RIR databaseRIPE 671 100% 67
193.34.202.0/24 Valid RIR databaseRIPE 671 100% 67
193.221.93.0/24 Valid RIR databaseRIPE 671 100% 67
193.221.120.0/24 Valid RIR databaseRIPE 671 100% 67
193.221.123.0/24 Valid RIR databaseRIPE 671 100% 67
193.221.219.0/24 Valid RIR databaseRIPE 671 100% 67
195.210.52.0/23 Valid RIR databaseRIPE 671 100% 67
2a02:80::/32 Valid RIR databaseRIPE 636 100% 67
2a02:1610::/32 Valid RIR databaseRIPE 636 100% 67
2a02:80::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS34244: RIPE::AS-TELESERVICE. 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 (AS34244 isn't in the set, or no route object for AS34244 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 objectsAS34244 in itNot covered
RIPE::AS-TELESERVICE RIPE 118280 Yes 0

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

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.253.60.0/24No ROA covers it. Add a ROA for AS34244, maxLength 24.671 of 673
ROA: none193.42.21.0/24No ROA covers it. Add a ROA for AS34244, maxLength 24.671 of 673

Route objects not announced

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

2001:67c:654::/48RIPENo 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.