Content Network · Europe

Peering AS205845

PLANISWARE EUROPE · AS-PLANISWARE

AS205845 is the content network operated by Planisware Europe across Western Europe. We maintain a dual-stack presence on major exchanges and welcome peering that shortens AS-paths to our services.

AS205845
Main ASN
8 IXPs
Peering points
5
Facilities
1–5 Gbps
Traffic level
IPv4 + IPv6
Dual stack
01 · Who we are

About

AS205845 is operated by Planisware Europe (also known as Planisware). It is a content network with a European geographic scope, carrying mostly outbound traffic toward our hosted services and platforms.

Our PeeringDB record is the authoritative source for up-to-date contacts, IXP presence and prefix limits: ⎋ PeeringDB / AS205845. Our public looking glass is available at lg.as205845.net, and service status at status.planisware.com.

This page defines the requirements to establish a peering relationship with us.

02 · Network details

Network

Key technical attributes of AS205845, mirrored from our PeeringDB record. Always treat PeeringDB as the source of truth for live values.

ASN
AS205845
IRR as-set
AS-PLANISWARE
Network type
Content
Geographic scope
Europe
Traffic level
1–5 Gbps
Traffic ratio
Mostly outbound
IPv4 prefixes
5
IPv6 prefixes
10
Protocols
Unicast IPv4 · IPv6
Looking glass
03 · Public peering

Internet exchange points

AS205845 is present on the following exchanges and peers with the route servers at each. We are happy to set up bilateral sessions on request.

ExchangeCapacityIPv4IPv6RS peer
CIXP — CERN Internet eXchange Point1G192.65.185.1782001:7f8:1c:24a:324:1500:0:1
DE-CIX Marseille10G185.1.47.1432001:7f8:36:0:3:2415:0:1
DE-CIX Munich10G185.1.208.2232001:7f8:44:0:3:2415:0:1
France-IX Marseille10G37.49.232.1572001:7f8:54:5::157
France-IX Paris10G37.49.238.1502001:7f8:54::2:150
Hopus10G37.77.34.652a02:e5c:1:26::2
Hopus10G37.77.39.252a02:e5c:5:c::2
SwissIX10G91.206.52.1962001:7f8:24:0:3:2415:0:1
04 · Footprint

Interconnection facilities

Datacenters where AS205845 is present for private interconnection (PNI) and cross-connects.

FacilityCityCountry
🇫🇷 France
Equinix PA3 — Paris, Saint-DenisParisFrance
Equinix PA10 — Paris, Saint-DenisParisFrance
🇨🇭 Switzerland
Equinix GV1 — GenevaGenevaSwitzerland
Equinix ZH5 — Zurich, SouthZurichSwitzerland
🇩🇪 Germany
Equinix MU4 — Munich, DornachAschheimGermany
05 · Policies

Peering policy

General policy
Restrictive
Multiple locations
Not required
Ratio requirement
No
Contract requirement
Not required

Introduction

AS205845 operates a restrictive peering policy. As a content network with mostly outbound traffic, we prioritise interconnections that reduce AS-path length to our services and provide clear mutual benefit. We have no traffic ratio requirement and no contract requirement, and peering at multiple locations is not required.

Peering is offered on a best-effort, good-faith basis. Partners agree not to hold AS205845 liable for any loss or damage caused by interruption of a peering session.

Requirements

Traffic requirements

Public peering

No minimum

No traffic threshold — the mutual benefit (typically AS-path shortening) must be clear. Sessions are established over the route servers or bilaterally.

Private peering (PNI)

On request

Available at our Equinix facilities. Contact us to discuss capacity and the terms of a cross-connect.

Ratio

No requirement

As a mostly-outbound content network, we apply no traffic-ratio requirement to peers.

Configuration

Route exchange is done over BGP only. AS205845 announces the routes registered under the as-set AS-PLANISWARE. Maximum-prefix values follow those published on PeeringDB and may change without notice — partners are encouraged to track them automatically. Never send traffic toward destinations not announced by AS205845, and never configure a static default route toward us.

06 · Routing

Routing & BGP policies

Global rules — filtered routes (dropped)

RIPE / ARIN / APNIC / AFRINIC objects must exist and be current for routes to be accepted.

BGP communities

The communities below may be used by peers and customers. Evaluated on a first-match-wins basis.

Local preference

CommunityLocal prefDescription
(default)10000Customer
205845:509950Customer backup
(default)1750Peer
205845:601700Peer backup
(default)750Transit
65535:05Graceful shutdown

Blackhole

AS205845 supports the well-known blackhole community defined in RFC 7999:

⚠ Note: Unauthorised use of the BLACKHOLE community can cause a denial-of-reachability attack. AS205845 only accepts this community from its customers, and only for IPs within authorised, filtered scopes.

AS-path prepending

AS-path prepending is allowed to influence route preference on the network.

07 · Get connected

Peering request

Partners must have an up-to-date PeeringDB account. Reach our peering team directly or open a request via PeeringDB.

Ready to peer with AS205845?

Send us your ASN and PeeringDB link, and we'll get back to you to set up the session.

⎋ Open our PeeringDB page
peering · peering@as205845.net
abuse · abuse@as205845.net