bgpreport

Network · data from 2026-11-12

AS204582 TCI-AS "The Technical center of Internet" Limited Liability Company

Registry name: TCI-AS "The Technical center of Internet" Limited Liability Company, RU · not in PeeringDB

28IPv4 routes 96.4% RPKI valid · 100.0% with a route object
11IPv6 routes 90.9% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS204582, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204582, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
62.76.254.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:6d0:ffc8::/48 No ROA RIR databaseRIPE 635 100% 67
62.76.248.0/24 Valid RIR databaseRIPE 673 100% 66
62.76.251.0/24 Valid RIR databaseRIPE 673 100% 66
62.76.252.0/24 Valid RIR databaseRIPE 673 100% 66
62.76.255.0/24 Valid RIR databaseRIPE 673 100% 66
185.133.1.0/24 Valid RIR databaseRIPE 673 100% 66
185.133.2.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.31.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.77.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.78.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.79.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.116.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.117.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.118.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.119.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.120.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.123.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.124.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.125.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.126.0/24 Valid RIR databaseRIPE 673 100% 66
212.193.127.0/24 Valid RIR databaseRIPE 673 100% 66
62.76.249.0/24 Valid RIR databaseRIPE 672 100% 66
62.76.250.0/24 Valid RIR databaseRIPE 672 100% 66
185.133.0.0/24 Valid RIR databaseRIPE 672 100% 66
185.133.3.0/24 Valid RIR databaseRIPE 672 100% 66
212.193.121.0/24 Valid RIR databaseRIPE 672 100% 66
212.193.122.0/24 Valid RIR databaseRIPE 672 100% 66
45.89.22.0/24 Valid RIR databaseRIPE 671 100% 66
2a0e:eac0:2000::/44 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2001::/48 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2002::/48 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2003::/48 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2010::/44 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2013::/48 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2100::/44 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2101::/48 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2110::/44 Valid RIR databaseRIPE 635 100% 67
2a0e:eac0:2200::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS204582 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.

  • ROA: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none62.76.254.0/24No ROA covers it. Add a ROA for AS204582, maxLength 24.673 of 673
ROA: none2001:6d0:ffc8::/48No ROA covers it. Add a ROA for AS204582, maxLength 48.635 of 636

Route objects not announced

Route objects with origin AS204582 whose prefix no peer sees AS204582 announce. Many are kept on purpose (backup routes, space announced only in some places).

212.193.126.0/23RIPENo ROA
2a0e:eac0:2000::/48RIPEValid
2a0e:eac0:2010::/48RIPEValid
2a0e:eac0:2030::/44RIPEValid
2a0e:eac0:2100::/48RIPEValid
2a0e:eac0:2102::/48RIPEValid
2a0e:eac0:2110::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.