bgpreport

Network · data from 2026-11-12

AS268057 J C G SILVA INFORMATICA

Registry name: AS268057 - J C G SILVA INFORMATICA EIRELI, BR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS268057, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268057, 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.
45.168.108.0/23 Valid Other IRR onlyRADB 671 100% 66
45.168.111.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
45.168.110.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
45.168.108.0/22 Valid Other IRR onlyRADB 665 99% 67
2804:574c::/32 Valid Other IRR onlyRADB, TC 630 99% 67
45.168.108.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
45.168.109.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS268057: AS268057:AS-CUSTOMERS. 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 (AS268057 isn't in the set, or no route object for AS268057 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 objectsAS268057 in itNot covered
AS268057:AS-CUSTOMERS TC 010 No 7

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

  • Route object: RIR7
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: RIR45.168.108.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.168.111.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.168.110.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.108.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:574c::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR45.168.108.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.168.109.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
AS-SET: own ASNAS268057:AS-CUSTOMERSAS268057 isn't in AS268057:AS-CUSTOMERS (TC) once expanded. Add AS268057 to it.

Route objects not announced

Every route object with origin AS268057 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.