bgpreport

Network · data from 2026-11-12

AS208185 NETGATE-SOLUTION-AS Net Gate Telecom S.R.L.

Registry name: NETGATE-SOLUTION-AS Net Gate Telecom S.R.L., RO · not in PeeringDB

19IPv4 routes 5.3% RPKI valid · 0.0% with a route object
0IPv6 routes
10RPKI invalid 10 origin · 0 maxLength
8No ROA 19 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
31Route objects not announced registered with origin AS208185, seen from no peer

Announced routes

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

151.241.136.0/24 Invalid: origin None 2 0%low visibility 2
151.241.137.0/24 Invalid: origin None 2 0%low visibility 2
151.241.138.0/24 Invalid: origin None 2 0%low visibility 2
151.241.139.0/24 Invalid: origin None 2 0%low visibility 2
151.241.164.0/24 Invalid: origin None 2 0%low visibility 2
151.241.165.0/24 Invalid: origin None 2 0%low visibility 2
151.241.166.0/24 Invalid: origin None 2 0%low visibility 2
151.241.167.0/24 Invalid: origin None 2 0%low visibility 2
195.211.190.0/24 Invalid: origin None 2 0%low visibility 2
77.90.177.0/24 Invalid: origin Other origin only 1 0%low visibility 1
77.110.65.0/24 No ROA None 2 0%low visibility 2
77.110.72.0/24 No ROA None 2 0%low visibility 2
77.110.89.0/24 No ROA None 2 0%low visibility 2
80.71.153.0/24 No ROA None 2 0%low visibility 2
94.183.248.0/24 No ROA None 2 0%low visibility 2
94.183.249.0/24 No ROA None 2 0%low visibility 2
94.183.250.0/24 No ROA None 2 0%low visibility 2
94.183.251.0/24 No ROA None 2 0%low visibility 2
109.160.33.0/24 Valid Other origin only 2 0%low visibility 2

AS-SET

AS208185 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 68 are in fix.csv.

  • ROA: origin10
  • ROA: none8
  • Route object: none19
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: origin151.241.136.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.136.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.137.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.137.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.138.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.138.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.139.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.139.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.164.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.164.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.165.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.165.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.166.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.166.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin151.241.167.0/24ROAs covering it name AS834, not AS208185. If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none151.241.167.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin195.211.190.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS208185 should announce it, add a ROA for AS208185.2 of 673
Route object: none195.211.190.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: origin77.90.177.0/24ROAs covering it name AS42821, not AS208185. If AS208185 should announce it, add a ROA for AS208185.1 of 673
Route object: none77.90.177.0/24Route objects for it name AS42821. Add a route object with origin AS208185 in the RIR database for the space.1 of 673
ROA: none77.110.65.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none77.110.65.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none77.110.72.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none77.110.72.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none77.110.89.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none77.110.89.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none80.71.153.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none80.71.153.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none94.183.248.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none94.183.248.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none94.183.249.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none94.183.249.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none94.183.250.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none94.183.250.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
ROA: none94.183.251.0/24No ROA covers it. Add a ROA for AS208185, maxLength 24.2 of 673
Route object: none94.183.251.0/24No route object for it. Add a route object with origin AS208185 in the RIR database for the space.2 of 673
Route object: none109.160.33.0/24Route objects for it name AS25211. Add a route object with origin AS208185 in the RIR database for the space.2 of 673

Route objects not announced

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

77.47.144.0/22RIPEValid
81.90.25.0/24RIPEInvalid: origin
93.152.209.0/24RIPEInvalid: origin
94.154.45.0/24RIPEInvalid: origin
102.135.2.0/24AFRINICNo ROA
102.135.29.0/24AFRINICNo ROA
102.135.41.0/24AFRINICNo ROA
102.135.48.0/24AFRINICNo ROA
102.135.88.0/24AFRINICValid
115.167.73.0/24APNICValid
115.167.76.0/24APNICValid
115.167.77.0/24APNICValid
115.167.78.0/24APNICValid
172.111.160.0/24ARINValid
185.84.157.0/24RIPEValid
207.121.32.0/21ALTDBNo ROA
209.244.96.0/22ALTDBNo ROA
209.244.100.0/22ALTDBNo ROA
209.244.154.0/24ALTDBNo ROA
209.244.155.0/24ALTDBNo ROA
216.85.240.0/21ALTDBNo ROA
216.202.5.0/24ALTDBNo ROA
216.202.46.0/24ALTDBNo ROA
216.202.47.0/24ALTDBNo ROA
216.202.48.0/22ALTDBNo ROA
216.202.48.0/24ALTDBNo ROA
216.202.49.0/24ALTDBNo ROA
216.202.50.0/24ALTDBNo ROA
216.202.51.0/24ALTDBNo ROA
216.202.52.0/24ALTDBNo ROA
216.202.53.0/24ALTDBNo 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.