bgpreport

Network · data from 2026-11-12

AS13246 InterNetWire Communications GmbH

Registry name: INETWIRE-AS Key-Systems GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13246, 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.
80.86.1.0/24 No ROA None 2 0%low visibility 2
95.130.23.0/24 Valid RIR databaseRIPE 673 100% 67
95.130.17.0/24 Valid RIR databaseRIPE 670 100% 67
95.130.16.0/21 Valid RIR databaseRIPE 669 99% 67
95.130.16.0/24 Valid RIR databaseRIPE 667 99% 67
95.130.18.0/24 Valid RIR databaseRIPE 667 99% 67
95.130.20.0/24 Valid RIR databaseRIPE 667 99% 67
95.130.21.0/24 Valid RIR databaseRIPE 667 99% 67
95.130.22.0/24 Valid RIR databaseRIPE 667 99% 67
185.181.192.0/22 Valid RIR databaseRIPE 667 99% 67
2a02:2940:3::/48 Valid RIR databaseRIPE 636 100% 67
2a02:2940::/48 Valid RIR databaseRIPE 634 100% 67
2a02:2940::/32 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none80.86.1.0/24No ROA covers it. Add a ROA for AS13246, maxLength 24.2 of 673
Route object: none80.86.1.0/24No route object for it. Add a route object with origin AS13246 in the RIR database for the space.2 of 673

Route objects not announced

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

95.130.19.0/24RIPEValid
185.181.192.0/24RIPEInvalid: maxLength
185.181.193.0/24RIPEInvalid: maxLength
185.181.194.0/24RIPEInvalid: maxLength
185.181.195.0/24RIPEValid

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.