bgpreport

Network · data from 2026-11-12

AS265279 Soft System Informatica

Registry name: AS265279 - Soft System Informatica Ltda, BR · PeeringDB

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

Announced routes

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

167.250.24.0/22 Valid Other IRR onlyTC 672 100% 67
167.250.24.0/23 Valid Other IRR onlyTC 672 100% 67
168.195.144.0/22 Valid Other IRR onlyTC 672 100% 67
168.195.146.0/23 Valid Other IRR onlyTC 672 100% 67
167.250.26.0/23 Valid Other IRR onlyTC 671 100% 67
168.195.144.0/23 Valid Other IRR onlyTC 671 100% 67
200.215.240.0/22 Valid Other IRR onlyTC 671 100% 67
200.215.240.0/23 Valid Other IRR onlyTC 671 100% 67
200.215.242.0/23 Valid Other IRR onlyTC 671 100% 67
2804:2d64::/32 Valid Other IRR onlyTC 631 99% 67
2804:2d64::/36 Valid Other IRR onlyTC 83 13% 32
167.250.24.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
167.250.25.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
167.250.26.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
167.250.27.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
168.195.144.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
168.195.145.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
168.195.146.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
168.195.147.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
200.215.240.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
200.215.241.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
200.215.242.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
200.215.243.0/24 Valid Other IRR onlyTC 24 4%low visibility 12
2804:2d64::/40 Valid Other IRR onlyTC 14 2%low visibility 9

AS-SET

PeeringDB's irr_as_set for AS265279: AS265279:AS-SOFT_SYSTEM-TELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265279 isn't in the set, or no route object for AS265279 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265279 in itNot covered
AS265279:AS-SOFT_SYSTEM-TELECOM TC 1224 Yes 0

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

  • Route object: RIR24
ChangePrefix or setDetailFull-table peers
Route object: RIR167.250.24.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR167.250.24.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.195.144.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.195.146.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR167.250.26.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.195.144.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.215.240.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.215.240.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.215.242.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2d64::/32Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2d64::/36Route object only in TC. Add it in the RIR database for the space.83 of 636
Route object: RIR167.250.24.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR167.250.25.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR167.250.26.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR167.250.27.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR168.195.144.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR168.195.145.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR168.195.146.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR168.195.147.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR200.215.240.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR200.215.241.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR200.215.242.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR200.215.243.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR2804:2d64::/40Route object only in TC. Add it in the RIR database for the space.14 of 636

Route objects not announced

Every route object with origin AS265279 is announced.

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.