RPKI or IRR
We only accept a prefix when it has a valid RPKI ROA or a route object in a recognised IRR that matches your ASN. RPKI-invalid routes are dropped.
Network
One autonomous system, registered through the RIPE NCC, with three upstreams in its routing policy. Every fact below has a public record you can check.
| ASN | AS203334 |
|---|---|
| AS name | Carvidmarine |
| Registry | RIPE NCC |
| Assigned | 2025-11-28 |
| Holder | Carvidmarine LLC (ORG-CL821-RIPE) |
| Upstreams | AS209735 · AS207841 · AS44355 |
| Announcements | Not live yet. Customer addresses are currently assigned from upstream allocations. |
| Abuse | [email protected] |
Routing policy
We only accept a prefix when it has a valid RPKI ROA or a route object in a recognised IRR that matches your ASN. RPKI-invalid routes are dropped.
Each session has a max-prefix limit based on your registered address space, plus some room to grow. Ask us to raise it before you add new blocks.
IPv4 longer than /24 and IPv6 longer than /48 are filtered, except /32 and /128 routes tagged for blackholing. Bogons and default routes are filtered too. Routes you learn from your own transit providers are rejected.
BGP communities
Tag the routes you send us to ask for an address under attack to be blackholed, keep a prefix away from our upstreams or make a path less attractive. Every transit session accepts them from the day the session comes up.
Before your session goes up, we add your ASN and prefixes to our routing registry objects so our upstreams accept them.
| Community | Action |
|---|---|
| 203334:666 | Blackhole, /32 and /128 only, where the upstream supports it |
| 203334:0 | Do not announce to any upstream |
| 203334:1 | Prepend once to all upstreams |
| 203334:2 | Prepend twice to all upstreams |
We're taking settlement-free peering requests now, and sessions open once our announcements are live. Send your ASN, facility and expected traffic to [email protected].