bgpreport

Network · data from 2026-11-12

AS219048 SUN-IT-SOLUTIONS Sachin Kothawade trading as SUN IT SOLUTIONS

Registry name: SUN-IT-SOLUTIONS Sachin Kothawade trading as SUN IT SOLUTIONS, IN · not in PeeringDB

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

Announced routes

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

89.31.239.0/24 Invalid: origin Other origin only 2 0%low visibility 2
217.60.74.0/24 Invalid: origin Other origin only 2 0%low visibility 1
151.247.84.0/22 Invalid: origin None 1 0%low visibility 1
31.58.242.0/24 No ROA None 2 0%low visibility 1
217.60.75.0/24 No ROA None 2 0%low visibility 1

AS-SET

AS219048 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 18 are in fix.csv.

  • ROA: origin3
  • ROA: none2
  • Route object: none5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin89.31.239.0/24ROAs covering it name AS834, AS8851, AS19905, not AS219048. If AS219048 should announce it, add a ROA for AS219048.2 of 673
Route object: none89.31.239.0/24Route objects for it name AS834. Add a route object with origin AS219048 in the RIR database for the space.2 of 673
ROA: origin217.60.74.0/24ROAs covering it name AS24940, not AS219048. If AS219048 should announce it, add a ROA for AS219048.2 of 673
Route object: none217.60.74.0/24Route objects for it name AS24940. Add a route object with origin AS219048 in the RIR database for the space.2 of 673
ROA: origin151.247.84.0/22ROAs covering it name AS834, not AS219048. If AS219048 should announce it, add a ROA for AS219048.1 of 673
Route object: none151.247.84.0/22No route object for it. Add a route object with origin AS219048 in the RIR database for the space.1 of 673
ROA: none31.58.242.0/24No ROA covers it. Add a ROA for AS219048, maxLength 24.2 of 673
Route object: none31.58.242.0/24No route object for it. Add a route object with origin AS219048 in the RIR database for the space.2 of 673
ROA: none217.60.75.0/24No ROA covers it. Add a ROA for AS219048, maxLength 24.2 of 673
Route object: none217.60.75.0/24No route object for it. Add a route object with origin AS219048 in the RIR database for the space.2 of 673

Route objects not announced

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

5.56.29.0/24RIPEValid
5.230.166.0/24RIPEValid
31.59.176.0/21RADBNo ROA
31.59.176.0/24RIPEValid
31.59.177.0/24RIPEValid
87.76.192.0/24RADB, RIPEValid
89.251.24.0/24RIPEValid
2a14:ae00:110::/48RIPEValid

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.