Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS9123 (TimeWeb-AS JSC "TIMEWEB") announces 930 IPv4 and 36 IPv6 prefixes. 1 warning
| AS page | AS9123 |
|---|---|
| Holder | TimeWeb-AS JSC "TIMEWEB" |
| Allocation | RIPE NCC, Russia (RU), allocated 2008-04-01 |
| Prefixes (IPv4 / IPv6) | 930 / 36 |
| RPKI valid | 100% (966 / 966) |
| Upstreams and peers | 59 |
| Peering policy | Open |
What to fix
-
Warning
8 of 966 announced prefixes have no IRR route object: 85.239.37.0/24, 2a03:6f00:c::/48, 2a03:6f00:13::/48, 2a03:6f02::/48, 2a03:6f02:2::/48 (+3).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS9123 in your RIR’s IRR database (or RADB).
route: 85.239.37.0/24 origin: AS9123 route6: 2a03:6f00:c::/48 origin: AS9123 route6: 2a03:6f00:13::/48 origin: AS9123
Checks
Routing and RPKI 8 of 966 announced prefixes have no IRR route object: 85.239.37.0/24, 2a03:6f00:c::/48, 2a03:6f00:13::/48, 2a03:6f02::/48, 2a03:6f02:2::/48 (+3).
- Pass: AS9123 announces 930 IPv4 and 36 IPv6 prefixes.
- Pass: All 966 announced prefixes are RPKI valid.
- Warning: 8 of 966 announced prefixes have no IRR route object: 85.239.37.0/24, 2a03:6f00:c::/48, 2a03:6f00:13::/48, 2a03:6f02::/48, 2a03:6f02:2::/48 (+3).
- Info: 59 upstreams and peers, 12 downstream networks seen.
| Holder | TimeWeb-AS JSC "TIMEWEB" |
|---|---|
| IPv4 prefixes | 930 |
| IPv6 prefixes | 36 |
| RPKI | 966 valid |
| Without IRR route object | 8 |
| Downstream networks | 12 |
Upstreams and peers seen to the left 59
Announced prefixes 966
Showing the first 100.
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | TimeWeb-AS |
|---|---|
| Handle | AS9123 |
| Range | AS9123 |
| Status | active |
| Registered | 2008-04-01T10:36:48Z |
| Last changed | 2026-11-06T14:11:06Z |
| Abuse contact | abuse@timeweb.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2008-04-01 |
| Status | Allocated |
| Delegated range | AS9123 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | JSC "TIMEWEB" | |
| registrant | RIPE-NCC-END-MNT | |
| registrant | TIMEWEB-MNT | |
| abuse | TimeWeb Co. Ltd. Role Account | abuse@timeweb.ru |
Source: https://rdap.db.ripe.net/autnum/9123. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB AS9123 is in PeeringDB as JSC TimeWeb.
- Pass: AS9123 is in PeeringDB as JSC TimeWeb.
- Info: Peering policy: Open.
- Info: Present at 12 internet exchanges with 16 ports (1.6T in total).
| Network | JSC TimeWeb (TimeWeb.ru / Timeweb Cloud / TimeWeb Co. Ltd.) |
|---|---|
| AS number | AS9123 |
| Type | NSP, Global |
| Website | http://www.timeweb.ru |
| IRR as-set | RIPE::AS-TIMEWEB |
| Prefixes (IPv4 / IPv6) | 2000 / 500 |
| Traffic | 1-5Tbps, Mostly Outbound |
| Peering policy | Open |
| Policy URL | https://timeweb.com/ru/partners/peering-policy/ |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-11-03 |
| Technical | noc@timeweb.ru |
|---|---|
| Abuse | abuse@timeweb.ru |
| Policy | a.lazarev@timeweb.ru |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup