bgpreport

Network · data from 2026-11-12

AS268568 ImplantarTelecomNet

Registry name: AS268568 - IMPLANTAR TELECOM SOCIEDADE LIMITADA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
13IPv6 routes 69.2% RPKI valid · 46.2% with a route object
4RPKI invalid 4 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 AS268568, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268568, 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:58b0::/34 Invalid: origin None 1 0%low visibility 1
2804:58b0:4000::/34 Invalid: origin None 1 0%low visibility 1
2804:58b0:8000::/34 Invalid: origin None 1 0%low visibility 1
2804:58b0:c000::/34 Invalid: origin None 1 0%low visibility 1
2804:532c:134::/46 Valid Nonecovered by 2804:532c:130::/45 352 55% 65
2804:532c:138::/46 Valid Nonecovered by 2804:532c:138::/45 352 55% 65
2804:532c:130::/46 Valid Nonecovered by 2804:532c:130::/45 351 55% 65
45.163.144.0/23 Valid Other IRR onlyTC 669 99% 67
45.163.146.0/23 Valid Other IRR onlyTC 669 99% 67
45.163.144.0/22 Valid Other IRR onlyTC 668 99% 67
2804:532c::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:532c::/45 Valid Other IRR onlyTC 352 55% 65
2804:532c:128::/45 Valid Other IRR onlyTC 352 55% 65
2804:532c:120::/45 Valid Other IRR onlyTC 351 55% 65
2804:532c:130::/45 Valid Other IRR onlyTC 351 55% 65
2804:532c:138::/45 Valid Other IRR onlyTC 351 55% 65
45.163.147.0/24 Valid Other IRR onlyTC 4 1%low visibility 5
45.163.144.0/24 Valid Other IRR onlyTC 3 0%low visibility 3
45.163.145.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.163.146.0/24 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS268568: AS268568:AS-IMPLANTAR-ALL. 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 (AS268568 isn't in the set, or no route object for AS268568 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 objectsAS268568 in itNot covered
AS268568:AS-IMPLANTAR-ALL TC 6631,370 Yes 4

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.

  • ROA: origin4
  • Route object: none7
  • Route object: RIR13
ChangePrefix or setDetailFull-table peers
ROA: origin2804:58b0::/34ROAs covering it name AS268144, not AS268568. If AS268568 should announce it, add a ROA for AS268568.1 of 636
Route object: none2804:58b0::/34No route object for it. Add a route object with origin AS268568 in the RIR database for the space.1 of 636
ROA: origin2804:58b0:4000::/34ROAs covering it name AS268144, not AS268568. If AS268568 should announce it, add a ROA for AS268568.1 of 636
Route object: none2804:58b0:4000::/34No route object for it. Add a route object with origin AS268568 in the RIR database for the space.1 of 636
ROA: origin2804:58b0:8000::/34ROAs covering it name AS268144, not AS268568. If AS268568 should announce it, add a ROA for AS268568.1 of 636
Route object: none2804:58b0:8000::/34No route object for it. Add a route object with origin AS268568 in the RIR database for the space.1 of 636
ROA: origin2804:58b0:c000::/34ROAs covering it name AS268144, not AS268568. If AS268568 should announce it, add a ROA for AS268568.1 of 636
Route object: none2804:58b0:c000::/34No route object for it. Add a route object with origin AS268568 in the RIR database for the space.1 of 636
Route object: none2804:532c:134::/46No route object for it. A route object for 2804:532c:130::/45 with origin AS268568 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268568 in the RIR database for the space.352 of 636
Route object: none2804:532c:138::/46No route object for it. A route object for 2804:532c:138::/45 with origin AS268568 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268568 in the RIR database for the space.352 of 636
Route object: none2804:532c:130::/46No route object for it. A route object for 2804:532c:130::/45 with origin AS268568 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268568 in the RIR database for the space.351 of 636
Route object: RIR45.163.144.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.163.146.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.163.144.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:532c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:532c::/45Route object only in TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:532c:128::/45Route object only in TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:532c:120::/45Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:532c:130::/45Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:532c:138::/45Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR45.163.147.0/24Route object only in TC. Add it in the RIR database for the space.4 of 673
Route object: RIR45.163.144.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR45.163.145.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.163.146.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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