bgpreport

Network · data from 2026-11-12

AS43670 NTC-AS New Telecommunication Company Ltd.

Registry name: NTC-AS New Telecommunication Company Ltd., RU · not in PeeringDB

7IPv4 routes 71.4% RPKI valid · 85.7% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS43670, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43670, 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.

78.31.18.118/32 Invalid: maxLength Nonecovered by 78.31.18.0/24 1 0%low visibility 1
91.246.20.0/24 No ROA RIR databaseRIPE 673 100% 66
78.31.16.0/21 Valid RIR databaseRIPE 673 100% 66
91.246.16.0/22 Valid RIR databaseRIPE 673 100% 66
193.34.208.0/22 Valid RIR databaseRIPE 673 100% 66
193.34.208.0/24 Valid RIR databaseRIPE 673 100% 66
193.34.210.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS43670 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 26 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: maxLength78.31.18.118/32ROA 78.31.16.0/21 AS43670 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 78.31.18.118/32.1 of 673
Route object: none78.31.18.118/32No route object for it. A route object for 78.31.18.0/24 with origin AS43670 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43670 in the RIR database for the space.1 of 673
ROA: none91.246.20.0/24No ROA covers it. Add a ROA for AS43670, maxLength 24.673 of 673

Route objects not announced

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

78.31.16.0/22RIPEInvalid: maxLength
78.31.16.0/24RIPEInvalid: maxLength
78.31.17.0/24RIPEInvalid: maxLength
78.31.18.0/24RIPEInvalid: maxLength
78.31.19.0/24RIPEInvalid: maxLength
78.31.20.0/22RIPEInvalid: maxLength
78.31.20.0/24RIPEInvalid: maxLength
78.31.21.0/24RIPEInvalid: maxLength
78.31.22.0/24RIPEInvalid: maxLength
78.31.23.0/24RIPEInvalid: maxLength
91.246.16.0/21RIPENo ROA
91.246.16.0/24RIPEInvalid: maxLength
91.246.17.0/24RIPEInvalid: maxLength
91.246.18.0/24RIPEInvalid: maxLength
91.246.19.0/24RIPEInvalid: maxLength
91.246.20.0/22RIPENo ROA
91.246.21.0/24RIPENo ROA
91.246.22.0/24RIPENo ROA
91.246.23.0/24RIPENo ROA
193.34.208.0/23RIPEInvalid: maxLength
193.34.209.0/24RIPEInvalid: maxLength
193.34.210.0/24RIPEInvalid: maxLength
193.34.211.0/24RIPEInvalid: maxLength

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.