bgpreport

Network · data from 2026-11-12

AS211422 OnlineInternet Emre Aydogan

Registry name: OnlineInternet Emre Aydogan, TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211422, 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.
77.47.142.0/24 Invalid: origin Other origin only 0 0%low visibility 1
195.178.130.0/24 Invalid: origin Other origin only 0 0%low visibility 1
45.115.24.0/24 No ROA Other origin only 665 99% 67
103.209.77.0/24 No ROA Other origin only 2 0%low visibility 1
109.160.33.0/24 Valid Other origin only 0 0%low visibility 1
5.181.87.0/24 Valid RIR databaseRIPE 672 100% 66
45.13.190.0/24 Valid RIR databaseRIPE 672 100% 66
94.154.36.0/24 Valid RIR databaseRIPE 672 100% 66
185.169.183.0/24 Valid RIR databaseRIPE 672 100% 67
185.174.20.0/24 Valid RIR databaseRIPE 672 100% 67
213.209.131.0/24 Valid RIR databaseRIPE 672 100% 67
5.181.85.0/24 Valid RIR databaseRIPE 671 100% 66
45.143.96.0/24 Valid RIR databaseRIPE 671 100% 67
77.90.175.0/24 Valid RIR databaseRIPE 671 100% 67
77.90.182.0/24 Valid RIR databaseRIPE 671 100% 67
94.154.45.0/24 Valid RIR databaseRIPE 671 100% 67
213.209.129.0/24 Valid RIR databaseRIPE 671 100% 67
45.221.68.0/24 Valid RIR databaseAFRINIC 670 100% 67
102.135.106.0/24 Valid RIR databaseAFRINIC 669 99% 67
213.209.152.0/24 Valid RIR databaseRIPE 669 99% 67
77.90.186.0/24 Valid RIR databaseRIPE 668 99% 67
185.148.243.0/24 Valid RIR databaseRIPE 666 99% 67
77.83.39.0/24 Valid RIR databaseRIPE 665 99% 66

AS-SET

AS211422 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: origin2
  • ROA: none2
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin77.47.142.0/24ROAs covering it name AS3319, AS25500, not AS211422. If AS211422 should announce it, add a ROA for AS211422.0 of 673
Route object: none77.47.142.0/24Route objects for it name AS3319. Add a route object with origin AS211422 in the RIR database for the space.0 of 673
ROA: origin195.178.130.0/24ROAs covering it name AS3319, not AS211422. If AS211422 should announce it, add a ROA for AS211422.0 of 673
Route object: none195.178.130.0/24Route objects for it name AS3319. Add a route object with origin AS211422 in the RIR database for the space.0 of 673
ROA: none45.115.24.0/24No ROA covers it. Add a ROA for AS211422, maxLength 24.665 of 673
Route object: none45.115.24.0/24Route objects for it name AS45629. Add a route object with origin AS211422 in the RIR database for the space.665 of 673
ROA: none103.209.77.0/24No ROA covers it. Add a ROA for AS211422, maxLength 24.2 of 673
Route object: none103.209.77.0/24Route objects for it name AS9009. Add a route object with origin AS211422 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 AS211422 in the RIR database for the space.0 of 673

Route objects not announced

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

172.111.160.0/24ARINValid
213.209.155.0/24RIPEValid

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.