bgpreport

Network · data from 2026-11-12

AS42942 Telecomp-AS Telecomp Ltd.

Registry name: Telecomp-AS Telecomp Ltd., BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42942, 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.
87.120.229.253/32 Valid Nonecovered by 87.120.228.0/23 5 1%low visibility 9
87.120.228.0/23 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS42942 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none87.120.229.253/32No route object for it. A route object for 87.120.228.0/23 with origin AS42942 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS42942 in the RIR database for the space.5 of 673

Route objects not announced

Every route object with origin AS42942 is announced.

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.