bgpreport

Network · data from 2026-11-12

AS205199 bitcom Bredbandig IT Communication i Goteborg AB

Registry name: bitcom Bredbandig IT Communication i Goteborg AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205199, 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.
193.17.202.0/24 No ROA RIR databaseRIPE 671 100% 67
45.134.120.0/22 Valid RIR databaseRIPE 671 100% 67
45.136.156.0/22 Valid RIR databaseRIPE 671 100% 67
45.138.140.0/22 Valid RIR databaseRIPE 671 100% 67
45.144.116.0/22 Valid RIR databaseRIPE 671 100% 67
45.150.160.0/22 Valid RIR databaseRIPE 671 100% 67
185.157.168.0/22 Valid RIR databaseRIPE 671 100% 67
185.241.172.0/22 Valid RIR databaseRIPE 671 100% 67
192.36.246.0/24 Valid RIR databaseRIPE 671 100% 67
192.121.11.0/24 Valid RIR databaseRIPE 671 100% 67
192.121.128.0/22 Valid RIR databaseRIPE 671 100% 67
193.42.219.0/24 Valid RIR databaseRIPE 671 100% 67
193.43.14.0/24 Valid RIR databaseRIPE 671 100% 67
193.43.28.0/24 Valid RIR databaseRIPE 671 100% 67
193.43.37.0/24 Valid RIR databaseRIPE 671 100% 67
193.180.192.0/23 Valid RIR databaseRIPE 671 100% 67
193.181.36.0/24 Valid RIR databaseRIPE 671 100% 67
193.181.44.0/24 Valid RIR databaseRIPE 671 100% 67
193.234.6.0/24 Valid RIR databaseRIPE 671 100% 67
193.234.97.0/24 Valid RIR databaseRIPE 671 100% 67
193.234.112.0/22 Valid RIR databaseRIPE 671 100% 67
194.35.78.0/24 Valid RIR databaseRIPE 671 100% 67
194.35.92.0/24 Valid RIR databaseRIPE 671 100% 67
194.35.95.0/24 Valid RIR databaseRIPE 671 100% 67
194.35.182.0/24 Valid RIR databaseRIPE 671 100% 67
194.147.242.0/23 Valid RIR databaseRIPE 671 100% 67
194.147.250.0/23 Valid RIR databaseRIPE 671 100% 67

AS-SET

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.17.202.0/24No ROA covers it. Add a ROA for AS205199, maxLength 24.671 of 673

Route objects not announced

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