bgpreport

Network · data from 2026-11-12

AS47959 TELINEA Telinea d.o.o.

Registry name: TELINEA Telinea d.o.o., BA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47959, 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.
46.23.110.0/26 Invalid: maxLength Nonecovered by 46.23.110.0/24 2 0%low visibility 2
46.23.110.64/26 Invalid: maxLength Nonecovered by 46.23.110.0/24 2 0%low visibility 2
46.23.110.128/26 Invalid: maxLength Nonecovered by 46.23.110.0/24 2 0%low visibility 2
104.239.103.0/24 No ROA RIR databaseRIPE 670 100% 68
46.23.110.0/24 Valid RIR databaseRIPE 670 100% 67
2a00:1b80::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS47959 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 11 are in fix.csv.

  • ROA: maxLength3
  • ROA: none1
  • Route object: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength46.23.110.0/26ROA 46.23.110.0/24 AS47959 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 46.23.110.0/26.2 of 673
Route object: none46.23.110.0/26No route object for it. A route object for 46.23.110.0/24 with origin AS47959 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47959 in the RIR database for the space.2 of 673
ROA: maxLength46.23.110.64/26ROA 46.23.110.0/24 AS47959 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 46.23.110.64/26.2 of 673
Route object: none46.23.110.64/26No route object for it. A route object for 46.23.110.0/24 with origin AS47959 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47959 in the RIR database for the space.2 of 673
ROA: maxLength46.23.110.128/26ROA 46.23.110.0/24 AS47959 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 46.23.110.128/26.2 of 673
Route object: none46.23.110.128/26No route object for it. A route object for 46.23.110.0/24 with origin AS47959 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47959 in the RIR database for the space.2 of 673
ROA: none104.239.103.0/24No ROA covers it. Add a ROA for AS47959, maxLength 24.670 of 673

Route objects not announced

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

2a00:1b80::/48RIPEInvalid: maxLength
2a00:1b80:1::/48RIPEInvalid: maxLength
2a00:1b80:2::/48RIPEInvalid: maxLength
2a00:1b80:3::/48RIPEInvalid: 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.