bgpreport

Network · data from 2026-11-12

AS212710 TeamViewer AMEA

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212710, 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.58.100.0/24 No ROA RIR databaseRIPE 671 100% 67
193.58.101.0/24 No ROA RIR databaseRIPE 671 100% 67
2a09:2900:8400::/40 No ROA RIR databaseRIPE 636 100% 67
2a09:2900::/48 No ROA RIR databaseRIPE 2 0%low visibility 2
2a09:2900:6000::/40 Valid RIR databaseRIPE 636 100% 67
2a09:2900:6800::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS212710'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 9 are in fix.csv.

  • ROA: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none193.58.100.0/24No ROA covers it. Add a ROA for AS212710, maxLength 24.671 of 673
ROA: none193.58.101.0/24No ROA covers it. Add a ROA for AS212710, maxLength 24.671 of 673
ROA: none2a09:2900:8400::/40No ROA covers it. Add a ROA for AS212710, maxLength 40.636 of 636
ROA: none2a09:2900::/48No ROA covers it. Add a ROA for AS212710, maxLength 48.2 of 636

Route objects not announced

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

193.58.100.0/22RIPENo ROA
193.58.102.0/24RIPENo ROA
193.58.103.0/24RIPENo ROA
2a09:2900::/29RIPENo ROA
2a09:2900:3000::/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.