bgpreport

Network · data from 2026-11-12

AS201236 NETCAST DOO BEOGRAD

Registry name: NETCAST-OBLAK-DOO NETCAST OBLAK d.o.o. Beograd, RS · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201236, 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.
185.26.116.0/23 No ROA Nonecovered by 185.26.116.0/22 673 100% 66
185.26.118.0/23 No ROA Nonecovered by 185.26.116.0/22 673 100% 66
185.17.188.0/22 No ROA RIR databaseRIPE 673 100% 66
185.17.188.0/23 No ROA RIR databaseRIPE 673 100% 66
185.17.190.0/23 No ROA RIR databaseRIPE 673 100% 66
185.26.116.0/22 No ROA RIR databaseRIPE 673 100% 66
194.53.124.0/22 No ROA RIR databaseRIPE 673 100% 66
194.53.124.0/23 No ROA RIR databaseRIPE 673 100% 66
194.53.126.0/23 No ROA RIR databaseRIPE 673 100% 66
2a05:7c00::/29 No ROA RIR databaseRIPE 634 100% 68

AS-SET

AS201236's PeeringDB record names no 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 25 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none185.26.116.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
Route object: none185.26.116.0/23No route object for it. A route object for 185.26.116.0/22 with origin AS201236 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201236 in the RIR database for the space.673 of 673
ROA: none185.26.118.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
Route object: none185.26.118.0/23No route object for it. A route object for 185.26.116.0/22 with origin AS201236 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201236 in the RIR database for the space.673 of 673
ROA: none185.17.188.0/22No ROA covers it. Add a ROA for AS201236, maxLength 22.673 of 673
ROA: none185.17.188.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
ROA: none185.17.190.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
ROA: none185.26.116.0/22No ROA covers it. Add a ROA for AS201236, maxLength 22.673 of 673
ROA: none194.53.124.0/22No ROA covers it. Add a ROA for AS201236, maxLength 22.673 of 673
ROA: none194.53.124.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
ROA: none194.53.126.0/23No ROA covers it. Add a ROA for AS201236, maxLength 23.673 of 673
ROA: none2a05:7c00::/29No ROA covers it. Add a ROA for AS201236, maxLength 29.634 of 636

Route objects not announced

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

109.245.208.0/25RIPEInvalid: origin
185.17.188.0/24RIPENo ROA
185.17.189.0/24RIPENo ROA
185.17.190.0/24RIPENo ROA
185.17.191.0/24RIPENo ROA
185.26.116.0/24RIPENo ROA
185.26.117.0/24RIPENo ROA
185.26.118.0/24RIPENo ROA
185.26.119.0/24RIPENo ROA
194.53.124.0/24RIPENo ROA
194.53.125.0/24RIPENo ROA
194.53.126.0/24RIPENo ROA
194.53.127.0/24RIPENo ROA

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.