Route server - Quito
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 207724235 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 200.1.6.1/32 | Route server - Quito | PEERINGDB | ASSIGNED | ● high |
| 2001:13c7:6006::5:2482:1/128 | Route server - Quito | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Route server” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Route server - Guayaquil 2 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- ROUTER-MONITORING-SERVER via Sunrise GmbH sub-allocation
- ROUTED-IPV6-BLOCK-ON-NZ-01-TUNNEL-SERVER-TID-2 via Zappie Host LLC sub-allocation
- ROUTED-IPV6-BLOCK-ON-NZ-01-TUNNEL-SERVER-TID-1 via Zappie Host LLC sub-allocation
- PIPEX-ROUTE-SERVER via Wavenet Limited sub-allocation
- Cust Route 1 via Netservers Limited sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
AS52482