bgpreport

Network · data from 2026-11-12

AS208175 TeamViewer EU

Registry name: TeamViewer-EU TeamViewer Germany GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208175, 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.
2a09:1500:7600::/40 No ROA RIR databaseRIPE 636 100% 67
185.245.28.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.29.0/24 Valid RIR databaseRIPE 673 100% 66
185.245.30.0/24 Valid RIR databaseRIPE 673 100% 66
2a09:1500:7000::/40 Valid RIR databaseRIPE 636 100% 69
2a09:1500:13::/48 Valid RIR databaseRIPE 635 100% 67
2a09:1500:2000::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:2400::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:4600::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:5400::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:5600::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:6600::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1501:3000::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1501:3800::/40 Valid RIR databaseRIPE 635 100% 67
2a09:1500:1000::/40 Valid RIR databaseRIPE 634 100% 67
2a09:1500:3400::/40 Valid RIR databaseRIPE 634 100% 69
2a09:1500:5800::/40 Valid RIR databaseRIPE 3 0%low visibility 3
2a09:1500::/48 Valid RIR databaseRIPE 2 0%low visibility 2
2a09:1500:8::/48 Valid RIR databaseRIPE 2 0%low visibility 2
2a09:1500:20::/48 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS208175'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 5 are in fix.csv.

  • ROA: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a09:1500:7600::/40No ROA covers it. Add a ROA for AS208175, maxLength 40.636 of 636

Route objects not announced

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

185.245.28.0/22RIPENo ROA
185.245.31.0/24RIPEValid
2a09:1500::/29RIPENo ROA
2a09:1501::/48RIPEValid

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.