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:
Transit Export Filters
Before propagation, transit routes undergo these sequential export filters:
Downstream Import Filters
For routes imported from downstream, the following filters are applied sequentially:
Communities
Each community tag instructs specific routing actions.
Action Communities
Do not announce to the specified AS
Prepend the AS once
Prepend the AS twice
Prepend the AS three times
Information Communities
Indicates the route was imported from upstream
Indicates the route was imported from an IX
Indicates the route was imported from downstream
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 Number | Type | Capacity | Description |
---|---|---|---|
216309 | Upstream | 10 Gbps | Main uplink in CO-1 |
212516 | Upstream | 1 Gbps | Backup uplink in CO-1 |
211138 | Upstream | 1 Gbps | DDoS protected uplink in CO-1 |
IRR Filters
We automatically generate IRR-based prefix filters every 6 hours, aggregating data from:
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.