AS25085 · Peering Policy

ALUE LTD Private · Research · Experimental

← AS25085

Peering Policy

AS25085 operates a restrictive, private-only peering policy. Sessions are established on a case-by-case basis at our discretion, evaluated against the criteria below. We do not offer open or public peering, and do not carry transit traffic for third parties.

Last reviewed June 2026 · PeeringDB ↗

Policy Type

Restrictive Private Only All peering requests are manually reviewed at our discretion

Technical

IPv6 Required

IPv4 Considered

Min. prefix IPv4 /24

Min. prefix IPv6 /48

RPKI Required · ROA validation enforced

IRR filtering Required

Administrative

PeeringDB Required · Up-to-date record

NOC contact Required · Best-effort response

AS-SET Required · Registered in IRR

Max prefixes Negotiated per session

Locations JP · GB · HK (active)

Traffic ratio No requirement

Contract None required

Session Conditions

No default route propagation

We do not accept default routes from peers, and do not advertise them. All announcements must be specific, registered prefixes.

No transit traffic

AS25085 does not carry transit for any third party. Peering sessions are strictly for the exchange of each network's own routes and customers.

Community tagging honoured

We accept and honour informational BGP communities where applicable. Action communities (blackholing, local-pref adjustment) are evaluated per request.

Route filtering is not optional

Both parties must implement prefix and AS-path filtering based on IRR and RPKI data. Sessions that cannot meet this requirement will not be established.

Graceful session management

Advance notice of planned maintenance or decommissioning is appreciated where possible. This is a privately operated network — response times may vary.

Common Rejection Reasons

Technical

— No valid RPKI ROA for announced prefixes

— Missing or incomplete IRR registration

— Announcement of prefixes longer than policy allows

— IPv6-only session not feasible on requested IXP

Administrative

— PeeringDB record absent or stale

— No reachable NOC or abuse contact

— Network involved in routing abuse incidents

— Peering request sent without identifying information

Contact & Process

Peering & NOC

[email protected]

Include your ASN, PeeringDB URL, and preferred location(s) in your initial message. Requests that omit this information may not receive a response.

Response time

Best-effort · No SLA

This network is privately operated. We aim to respond to all peering requests, but cannot commit to specific timelines.

Request process

01 Verify your PeeringDB record is current and your RPKI/IRR data is in order

↓

02 Email [email protected] with your ASN, AS-SET, PeeringDB link, and desired location(s)

↓

03 We review and confirm — session configuration follows upon mutual agreement