CHECK-UP NET TELECOM
Data as of 2026-09-13
BGP inherited
This organisation
| Netblocks | 39 · 4,101 IPv4 addresses |
| IPv6 | 8 prefixes (largest 2804:197c::/32) |
| Also registered under this name | 44 netblocks across 2 separate records |
| Record ID | 241238415 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (39)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.82.139/32 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 45.184.145.5/32 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 138.36.68.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.68.0/22 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.68.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.69.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.70.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.70.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 138.36.71.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 143.137.0.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 143.137.0.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 143.137.0.0/22 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 143.137.1.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 143.137.3.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.232.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.232.0/22 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.232.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.233.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.234.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.234.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 170.246.235.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 187.16.194.107/32 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.211.17/32 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.219.139.53/32 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.225.140.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.140.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.140.0/22 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.141.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.142.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.142.0/23 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 200.225.143.0/24 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 2001:12f8::211:17/128 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:2::54:139/128 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:3::53/128 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:13::145:5/128 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:17::107/128 | CHECK-UP NET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2804:197c::/33 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 2804:197c::/32 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
| 2804:197c:8000::/33 | CHECK-UP NET TELECOM | BGP | ANNOUNCED | ● high |
IPv6 ranges (8)
Footprint over time
12 weekly snapshots · JSON
43
+4 netblocks since 2026-07-05
2026-07-05
peak 43
2026-09-13
Network trust
what's this?
RPKI hygiene: D
how networks compare →
23.3%
of checked blocks have valid RPKI ROA coverage
(10 of 43)
No discrepancies found among checked blocks.
NIC Handles
10508614000132
AS61797
AS61797
CATLT28
CATLT28
CATLT28