bgpreport

Network · data from 2026-11-12

AS268239 Iconnect Serviços de Telecomunicações

Registry name: AS268239 - Iconnect Servicos de Telecomunicacoes LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268239, 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.
2804:4e18::/33 Valid Nonecovered by 2804:4e18::/32 86 14% 38
2804:4e18:8000::/33 Valid Nonecovered by 2804:4e18::/32 86 14% 38
45.236.38.0/24 Valid Nonecovered by 45.236.38.0/23 2 0%low visibility 2
2804:4e18::/34 Valid Nonecovered by 2804:4e18::/32 2 0%low visibility 2
2804:4e18:4000::/34 Valid Nonecovered by 2804:4e18::/32 2 0%low visibility 2
2804:4e18:8000::/34 Valid Nonecovered by 2804:4e18::/32 2 0%low visibility 2
2804:4e18:c000::/34 Valid Nonecovered by 2804:4e18::/32 2 0%low visibility 2
45.236.36.0/22 Valid Other IRR onlyALTDB, RADB 670 100% 67
2804:4e18::/32 Valid Other IRR onlyALTDB 633 100% 69
45.236.36.0/23 Valid Other IRR onlyRADB 96 14% 39
45.236.38.0/23 Valid Other IRR onlyRADB 96 14% 39
45.236.36.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
45.236.37.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
45.236.39.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS268239: AS-ICONNECTSFS. 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 (AS268239 isn't in the set, or no route object for AS268239 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 objectsAS268239 in itNot covered
AS-ICONNECTSFS ALTDB 117 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 14 are in fix.csv.

  • Route object: none7
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none2804:4e18::/33No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.86 of 636
Route object: none2804:4e18:8000::/33No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.86 of 636
Route object: none45.236.38.0/24No route object for it. A route object for 45.236.38.0/23 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.2 of 673
Route object: none2804:4e18::/34No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.2 of 636
Route object: none2804:4e18:4000::/34No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.2 of 636
Route object: none2804:4e18:8000::/34No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.2 of 636
Route object: none2804:4e18:c000::/34No route object for it. A route object for 2804:4e18::/32 with origin AS268239 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268239 in the RIR database for the space.2 of 636
Route object: RIR45.236.36.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4e18::/32Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
Route object: RIR45.236.36.0/23Route object only in RADB. Add it in the RIR database for the space.96 of 673
Route object: RIR45.236.38.0/23Route object only in RADB. Add it in the RIR database for the space.96 of 673
Route object: RIR45.236.36.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR45.236.37.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR45.236.39.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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