bgpreport

Network · data from 2026-11-12

AS208187 TeamViewer APAC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208187, 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:2700:8::/48 No ROA Nonecovered by 2a09:2700::/29 635 100% 67
2a09:2701::/32 No ROA Nonecovered by 2a09:2700::/29 2 0%low visibility 2
193.32.225.0/24 No ROA RIR databaseRIPE 673 100% 66
193.32.226.0/24 No ROA RIR databaseRIPE 671 100% 67
193.32.227.0/24 No ROA RIR databaseRIPE 671 100% 67
2a09:2700:3600::/40 Valid RIR databaseRIPE 636 100% 67
2a09:2700:8200::/40 Valid RIR databaseRIPE 636 100% 67
2a09:2701:6000::/40 Valid RIR databaseRIPE 636 100% 67
2a09:2700:3800::/40 Valid RIR databaseRIPE 634 100% 67
2a09:2700:4800::/40 Valid RIR databaseRADB, RIPE 631 99% 69

AS-SET

AS208187'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.

  • ROA: none5
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2a09:2700:8::/48No ROA covers it. Add a ROA for AS208187, maxLength 48.635 of 636
Route object: none2a09:2700:8::/48No route object for it. A route object for 2a09:2700::/29 with origin AS208187 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208187 in the RIR database for the space.635 of 636
ROA: none2a09:2701::/32No ROA covers it. Add a ROA for AS208187, maxLength 32.2 of 636
Route object: none2a09:2701::/32No route object for it. A route object for 2a09:2700::/29 with origin AS208187 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208187 in the RIR database for the space.2 of 636
ROA: none193.32.225.0/24No ROA covers it. Add a ROA for AS208187, maxLength 24.673 of 673
ROA: none193.32.226.0/24No ROA covers it. Add a ROA for AS208187, maxLength 24.671 of 673
ROA: none193.32.227.0/24No ROA covers it. Add a ROA for AS208187, maxLength 24.671 of 673

Route objects not announced

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

193.32.224.0/22RIPENo ROA
193.32.224.0/24RIPENo ROA
2a09:2700::/29RIPENo ROA
2a09:2700::/48RIPENo ROA
2a09:2700:2800::/40RIPEValid
2a09:2700:4000::/40RIPEValid

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.