bgpreport

Network · data from 2026-11-12

AS267013 INTERNET SOLUTION PROVIDER TELECOM. LTDA ME

Registry name: AS267013 - INTERNET SOLUTION PROVIDER TELECOM. LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267013, 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.226.104.0/22 Valid Other IRR onlyTC 671 100% 67
45.226.105.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
45.226.107.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
2804:46d0::/32 Valid Other IRR onlyTC 635 100% 67
2804:46d0::/33 Valid Other IRR onlyTC 333 52% 65
2804:46d0::/34 Valid Other IRR onlyTC 333 52% 65
2804:46d0::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:1000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:2000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:3000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:4000::/34 Valid Other IRR onlyTC 333 52% 65
2804:46d0:4000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:5000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:6000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:7000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:8000::/33 Valid Other IRR onlyTC 333 52% 65
2804:46d0:8000::/34 Valid Other IRR onlyTC 333 52% 65
2804:46d0:8000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:9000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:a000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:b000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:c000::/34 Valid Other IRR onlyTC 333 52% 65
2804:46d0:c000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:d000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:e000::/36 Valid Other IRR onlyTC 333 52% 65
2804:46d0:f000::/36 Valid Other IRR onlyTC 333 52% 65
45.226.104.0/23 Valid Other IRR onlyTC 132 20% 45
45.226.104.0/24 Valid Other IRR onlyTC 132 20% 45
45.226.106.0/23 Valid Other IRR onlyRADB, TC 132 20% 45
45.226.106.0/24 Valid Other IRR onlyRADB, TC 132 20% 45

AS-SET

PeeringDB's irr_as_set for AS267013: AS267013:AS-ANNOUNCEMENTS. 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 (AS267013 isn't in the set, or no route object for AS267013 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 objectsAS267013 in itNot covered
AS267013:AS-ANNOUNCEMENTS TC 4262 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 30 are in fix.csv.

  • Route object: RIR30
ChangePrefix or setDetailFull-table peers
Route object: RIR45.226.104.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.226.105.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.226.107.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:46d0::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:46d0::/33Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0::/34Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:1000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:2000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:3000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:4000::/34Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:4000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:5000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:6000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:7000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:8000::/33Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:8000::/34Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:8000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:9000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:a000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:b000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:c000::/34Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:c000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:d000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:e000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:46d0:f000::/36Route object only in TC. Add it in the RIR database for the space.333 of 636
Route object: RIR45.226.104.0/23Route object only in TC. Add it in the RIR database for the space.132 of 673
Route object: RIR45.226.104.0/24Route object only in TC. Add it in the RIR database for the space.132 of 673
Route object: RIR45.226.106.0/23Route object only in RADB, TC. Add it in the RIR database for the space.132 of 673
Route object: RIR45.226.106.0/24Route object only in RADB, TC. Add it in the RIR database for the space.132 of 673

Route objects not announced

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