AS41066 JSC RTComm.RU #56,042
IPv4 addresses
4,864
IPv6 /48 networks
0
RPKI
0 valid7 no ROA
Peers and downstreams
0
Holder
- AS name
- RTCOMM-SIBIR-AS
- Description
- JSC RTComm.RU
- Organisation
- JSC RTComm.RU
- Registered in
- Moscow, Russia
- Abuse contact
- abuse@rtcomm.ru
- Assigned
- 2006-06-07
- Registered
- 2006-06-08
- Record last changed
- 2024-02-15 05:20 UTC
None announced.
| AS12389 | PJSC Rostelecom ROSTELECOM-AS |
None seen.
None seen.
Upstream graph
Upstreams and their upstreams, from BGP pathsNetwork rating
#56,042 of 123,606 · 30.8/100| Customer cone weight 27%, 0 networks behind this AS |
0 |
| Announced address space weight 22% |
57 |
| Peers and providers weight 16% |
10 |
| Registry record weight 11% |
70 |
| Routing stability weight 11% |
80 |
| RPKI and IPv6 weight 13% |
0 |
Network health
Grade D · 45/100| fail | Prefixes covered by valid ROAs 0 of 7 announced prefixes are RPKI valid, 7 have no ROA. |
0/25 |
| pass | No RPKI invalid announcements None of the announcements is RPKI invalid. |
10/10 |
| fail | Announces IPv6 No IPv6 prefixes are announced. |
0/15 |
| partly | More than one upstream 1 upstream seen in BGP. |
5/10 |
| pass | Working abuse contact abuse@rtcomm.ru is published. |
15/15 |
| fail | Publishes a geofeed No geofeed found. Without one, location databases have to guess. |
0/10 |
| pass | No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger. |
10/10 |
| pass | Registry record maintained Last changed 2024-02-15. |
5/5 |
Routing changes
Last 30 daysNo changes recorded in the last 30 days. Changes are recorded each time the routing data of this AS is refreshed. Get alerts in real time.
WHOIS
aut-num: AS41066 as-name: RTCOMM-SIBIR-AS org: ORG-RA25-RIPE remarks: +--------------------------------------------------------------- remarks: | remarks: | External communities may be set by external peers when remarks: | talking to AS41066. remarks: | remarks: | Community Meaning remarks: | remarks: | 41066:170x When advertising to any uplink remarks: | 41066:171x When advertising to TTK uplink remarks: | 41066:172x When advertising to Beeline uplink remarks: | remarks: | 41066:120x When advertising to any peering remarks: | 41066:121x When advertising NSK-IX peering remarks: | 41066:122x When advertising Rostelecom peering remarks: | remarks: | ...x=0 - do not advertise remarks: | ...x=1,2,4 or 6 - prepend 41066 (1,2,4 or 6) times remarks: | remarks: | 41066:1900 BACKUP community. Local preference is set to 100, remarks: | which is the lowest value used in the network. remarks: | We DO NOT accept "no-export" community. remarks: +--------------------------------------------------------------- remarks: | 41066:666 - blackhole (discard) traffic remarks: +--------------------------------------------------------------- remarks: | Any other 41066:XXX communities are deleted. remarks: | remarks: | CUSTOMER - Peers routes are getting local preference of 1000. remarks: | RUSSIAN - Peers routes are getting local preference of 700-740. remarks: | INTERNATIONAL - Peers routes and UPLINKS remarks: | are getting local preference in the range of 600-680 remarks: | remarks: | We are using prefix-list filters that were built according remarks: | to RIPE route-objects. remarks: | remarks: +--------------------------------------------------------------- remarks: | Routing policies are becoming so complex that a complete remarks: | description is beyond the scope of this document. remarks: +--------------------------------------------------------------- remarks: | NOTE - Filtering on /24 boundary is applied - we do not remarks: | reannounce any route more specific than a /24. remarks: +--------------------------------------------------------------- admin-c: RT-RU tech-c: RT-RU status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: AS8342-MNT created: 2006-06-08T08:10:17Z last-modified: 2024-02-15T05:20:54Z source: RIPE % 36 routing policy lines (import/export) not shown