eepyPaws networks — AS214513

header image: a paw with trans pride coloured base, and toe beans in the colours of the non-binary pride flag; the text next to it reads "eepyPaws networks" (with small "z"s ascending from the last s) and "AS214513" below it

the fluffy networking project

Hiya. This is AS214513 or eepyPaws :3

We strive to be the fluffiest network around. But of course, we can't be sure … feel free to prove us wrong by being even fluffier!

At some point, we will (hopefully) manage to create the content for https://eepypaws.net and serve it to creatures around the world …
Yet, for now: This is a small purrsonal computering thingy, run by a cuddly kittyfox who meows at other fluffy creatures.

PS: have you seen anycats yet? 🐈

peering policy

Our peering policy is kinda open. Yet … when it comes to details, just calling it "open" wouldn't be appropriate. So, when it comes to simple options / limited choices, AS214513 is listed as "selective".

There is no requirement for formal agreements. eepyPaws operates on a best-effort basis — no guarantees regarding availability or stability of the service(s) will be made.

We will usually be peering with IX route servers, but might manually add peers to allow or deny lists. Some routes/prefixes might be limited to prior approval of individual peers we personally know and/or feel comfortable with. (One might call it "bonus content", that is not generally announced via upstreams or route servers.)

Peerings with queermisic parties will be suspended or denied in the first place!
Route exchange with — as well as individual prefixes/addresses from — entities (mainly large corporations) that we view as harmful for the internet (or our world and lives in general) may be blocked without prior notice.

Incoming routes are subject to RPKI and/or IRR filtering. Announcements of private-use IP space and ASNs should be avoided and will be discarded.

eepyPaws will announce AS214513 with prefixes of 2a10:ccc3:ca70::/44 le 48.

peering facilities

We will (soon™) be available at LocIX Düsseldorf and Frankfurt.
You may also request peering on other sites where eepyPaws is present or via tunnel.

contact

If relevant, please also look at out contact information provided on the management/information pages of the IX involved.

For peering requests: peering+via_pp.@noc.eepypaws.net
For legal issues and abuse related requests: abuse+via_pp@noc.eepypaws.net

work in progress

This page and the information on it, is to be considered work in progress. The same is true for the network in general.
(Current plans for next steps include: adding an AS set and route set, making peering via LocIX (DUS+FRA) operational, establishing a connection to LocIX NL, setting up a looking glass, considering BGP.Exchange and EVIX, running anycast DNS & other services, …)

This page was last updated on 2024-09-01.