Informazioni di Rete

Informazioni dettagliate sulla configurazione e le politiche di routing della rete LakeNetworks

Transit Import Filters

Routes from transit providers are processed through the following sequential filters:

Default Route
Blocked
IP Bogon
Blocked
AS Bogon
Blocked
BGP Path > 50
Blocked
RPKI Invalid
Blocked
Prefix Length (IPv4 </24, IPv6 </48)
Blocked

Transit Export Filters

Before propagation, transit routes undergo these sequential export filters:

Default
Blocked
IP Bogon
Blocked
AS Bogon
Blocked
BGP Path > 50
Blocked
Bad Prefix Length
Blocked
RPKI Invalid
Blocked

Downstream Import Filters

For routes imported from downstream, the following filters are applied sequentially:

ASN_BOGON
Blocked
BGP Path > 50
Blocked
Bad Prefix Length
Blocked
Bogon IP
Blocked
RPKI Invalid
Blocked
Not in Allowed Prefixes
Blocked
Accepted Route
Accepted

Communities

Each community tag instructs specific routing actions.

Action Communities

6517:0:<dstasn>

Do not announce to the specified AS

6517:1:<dstasn>

Prepend the AS once

6517:2:<dstasn>

Prepend the AS twice

6517:3:<dstasn>

Prepend the AS three times

Information Communities

6517:100:<x>

Indicates the route was imported from upstream

6517:200:<x>

Indicates the route was imported from an IX

6517:300:<x>

Indicates the route was imported from downstream

6517:400:<x>

Indicates the route was imported from a peer

Our Providers

We maintain direct sessions with various upstreams, peers, and IXes. Below is a quick overview:

AS NumberTypeCapacityDescription
216309Upstream10 GbpsMain uplink in CO-1
212516Upstream1 GbpsBackup uplink in CO-1
211138Upstream1 GbpsDDoS protected uplink in CO-1

IRR Filters

We automatically generate IRR-based prefix filters every 6 hours, aggregating data from:

RPKIAFRINICARINAPNICLACNICRIPE

RADB is considered a higher-risk IRR, so it requires manual verification. If you need to force the usage of RADB, please open a support ticket explaining why you must use RADB.